| 3 | Approval of the Agenda | |
|---|---|---|
| R3-211400 | RAN3#112-e Meeting Agenda | Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-211401 | RAN3#111-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-211559 | List of E-mail Discussions | RAN3 Chairman |
| R3-211560 | Guidelines for RAN3 Electronic Meetings | RAN3 Chairman, RAN3 Vice-Chairs |
| 7 | General, protocol principles and issues | |
| R3-211402 | TR 30.531 v1.38.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-211760 | Discussions on Chapter 10 in S1AP and NGAP | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-211761 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-211762 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-212599 | CB: # 1_Ch10_corrections - Summary of email discussion | Ericsson - moderator |
| R3-212719 | TR 30.531 v1.38.1 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-212724 | TR 30.531 v1.38.2 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-212882 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| R3-212883 | Correction for Chapter 10 | Ericsson, Nokia, Nokia Shanghai-Bell, Huawei |
| 8.1 | New Incoming LSs | |
| R3-211410 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | CT1 |
| R3-211411 | LS on Information on the port number allocation solutions | CT4 |
| R3-211413 | Reply LS on AN-PDB and PER targets for satellite access | RAN1 |
| R3-211414 | LS on Agreements Pertaining to L1/L2-Centric Inter-Cell Mobility | RAN1 |
| R3-211415 | LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | RAN1 |
| R3-211416 | Reply LS on Cell Configuration within TA/RA to Support Allowed NSSAI | RAN2 |
| R3-211417 | Reply LS on restricting the rate per UE per network slice | RAN2 |
| R3-211419 | Reply LS on Sufficiency of Survival Time | RAN2 |
| R3-211420 | Reply LS on Rel-16 NR positioning Correction | RAN2 |
| R3-211421 | LS on E-CID LTE measurement in Rel-15 | RAN2 |
| R3-211425 | Reply LS on broadcasting gNB ID length in system information block | RAN2 |
| R3-211427 | Clarification request for eNPN features | RAN2 |
| R3-211429 | Reply LS on AN-PDB and PER targets for satellite access | RAN2 |
| R3-211430 | Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | RAN2 |
| R3-211431 | LS reply on QoE Measurement Collection | RAN2 |
| R3-211432 | LS on IoT-NTN basic architecture | RAN2 |
| R3-211433 | LS on Conditional Handover with SCG configuration scenarios | TSG RAN WG2 |
| R3-211434 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | RAN2 |
| R3-211435 | Response LS on Scheduling Location in Advance to reduce Latency | RAN2 |
| R3-211436 | Reply LS on network sharing with multiple SSBs in a carrier | RAN2 |
| R3-211438 | Reply LS to SA3 on FBS detection | RAN2 |
| R3-211439 | Reply LS on support of PWS over SNPN | RAN2 |
| R3-211440 | Reply LS on synchronization of Ethernet Compression | TSG RAN WG2 |
| R3-211441 | RE: Use of language in 3GPP Standards | IEEE 1588 working group |
| R3-211442 | Reply LS on QoE Measurement Collection for LTE | RAN |
| R3-211444 | Reply LS on making PSCell ID available at the SGW of EPC | SA2 |
| R3-211445 | LS on RACS capability detection with S1 and NG handover | SA2 |
| R3-211446 | Reply LS on clarification request for eNPN features | SA2 |
| R3-211447 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | SA2 |
| R3-211448 | Reply LS on PDU Session level "Expected UE activity behaviour" | SA2 |
| R3-211449 | Reply LS on IoT-NTN basic architecture | SA2 |
| R3-211450 | LS on System support for Multi-USIM devices | SA2 |
| R3-211451 | LS on Scheduling Location in Advance to reduce Latency | SA2 |
| R3-211455 | LS on Time Synchronization assistance parameters | 3GPP SA WG2 |
| R3-211456 | LS on E-RABs that cannot be handed over to 2G/3G or 5G | SA2 |
| R3-211458 | Reply to LS on UE location aspects in NTN | SA2 |
| R3-211459 | LS on User Plane Integrity Protection for eUTRA connected to EPC | SA3 |
| R3-211460 | LS on conclusion of security study for disaggregated gNB architecture | SA3 |
| R3-211461 | Reply LS on False Base Station Detection | SA3 |
| R3-211462 | Reply LS on 5MBS progress and issues to address | SA3 |
| R3-211464 | Reply LS on the user consent for trace reporting | SA3 |
| R3-211465 | Reply LS on UE location aspects in NTN | SA3-LI |
| R3-211466 | LS on Handover terminology | SA5 |
| R3-211467 | LS Reply on QoS Monitoring for URLLC | SA5 |
| R3-211468 | LS on the clarification of HO and/or reselection parameters ranges required by MLB | 3GPP SA5 |
| R3-211470 | LS on network sharing with multiple SSBs in a carrier | SA5 |
| R3-211502 | LS on PDB for new 5QI | SA2 |
| R3-211507 | Response LS on Handover terminology | Nokia, Nokia Shanghai Bell |
| R3-211508 | Ranges for mobility parameters for SON MLB/MRO | Nokia, Nokia Shanghai Bell |
| R3-211509 | Response LS on the clarification of HO and/or reselection parameters ranges required by MLB | Nokia, Nokia Shanghai Bell |
| R3-211511 | Response LS to SA5 on handover terminology | TSG RAN WG2 |
| R3-211512 | LS on introducing extended DRX for RedCap UEs | RAN2 |
| R3-211513 | LS on multiple TACs per PLMN | RAN2 |
| R3-211517 | Discussion on the possible impacts of a CHO with MR-DC operation | Nokia, Nokia Shanghai Bell |
| R3-211518 | Enabling CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-211519 | Enabling CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-211520 | Enabling CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-211521 | Response LS on Conditional Handover with SCG configuration scenarios | Nokia, Nokia Shanghai Bell |
| R3-211603 | E-CID LTE measurement in Rel-15 | Nokia, Nokia Shanghai Bell |
| R3-211604 | Clarification of E-CID Measurement Result | Nokia, Nokia Shanghai Bell, Huawei |
| R3-211605 | Clarification of E-CID Measurement Result | Nokia, Nokia Shanghai Bell, Huawei |
| R3-211616 | Revisiting the flexible gNB ID | Qualcomm Incorporated |
| R3-211617 | Support for handling unknown length of gNB identifier | Qualcomm Incorporated |
| R3-211618 | Support for handling unknown length of gNB identifier | Qualcomm Incorporated |
| R3-211625 | On RACS Capability Detection for S1 and NG handover | Qualcomm Incorporated, Vodafone |
| R3-211626 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-211627 | Detection of RACS support at target during N2/S1 handover | Qualcomm Incorporated, Vodafone |
| R3-211628 | [DRAFT] Reply LS on RACS capability detection with S1 and NG handover | Qualcomm Incorporated |
| R3-211629 | [DRAFT] Reply LS on LS on IoT-NTN basic architecture | Qualcomm Incorporated |
| R3-211630 | On Support for User Plane Integrity Protection in E-UTRAN | Qualcomm Incorporated |
| R3-211631 | [DRAFT] Reply LS on LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R3-211634 | Correction of Ethernet Compression | Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless, Deutsche Telekom |
| R3-211635 | Correction of Ethernet and ROHC Compression | Nokia, Nokia Shanghai Bell, Orange, Verizon Wireless, Deutsche Telekom |
| R3-211636 | Response LS on Synchronization of Ethernet compression | Nokia, Nokia Shanghai Bell, Orange |
| R3-211766 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-211767 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-211768 | Indicating E-RABs that cannot be handed over to 2G/3G or 5G | Ericsson |
| R3-211788 | Exploiting the use of gNB ID length | Nokia, Nokia Shanghai Bell, Bell Mobility, Verizon Wireless |
| R3-211789 | Response LS on Broadcasting gNB ID length in system information blocks | Nokia, Nokia Shanghai Bell, Bell Mobility, Verizon Wireless |
| R3-211793 | Discussion on L1/L2-Centric Mobility | Nokia, Nokia Shanghai Bell |
| R3-211807 | Discussion on RACS capability detection with S1 and NG handover | CATT |
| R3-211808 | [Draft] Reply LS on RACS capability detection with S1 and NG handover | CATT |
| R3-211890 | Correction of round trip delay drift rate for NTN scenarios | Nokia, Nokia Shanghai Bell, Thales |
| R3-211946 | Discussion on L1/L2-centric inter-cell mobility | Samsung |
| R3-211996 | Flexible gNB ID length | Huawei |
| R3-211997 | Flexible gNB ID length [FLEX_gNB_Len] | Huawei |
| R3-211998 | Discussion on handover terminology | Huawei |
| R3-211999 | [Draft] Reply LS on handover terminology | Huawei |
| R3-212000 | Discussion on the RAN part delay measurement without D1 for QoS Monitoring for URLLC | Huawei |
| R3-212001 | [Draft] Reply LS on LS Reply on QoS Monitoring for URLLC | Huawei |
| R3-212053 | Flexible gNB ID length [FLEX_gNB_Len] | Huawei |
| R3-212056 | Consideration of EHC mismatch status | Huawei |
| R3-212057 | Correction on EHC mismatch status | Huawei |
| R3-212060 | Discussion on REDCAP eDRX cycles | Huawei |
| R3-212061 | Consideration on making PSCell ID available at the SGW of EPC | Huawei |
| R3-212062 | Correction on UE Location Information | Huawei |
| R3-212063 | Correction on UE Location Information | Huawei |
| R3-212064 | [Draft] Reply LS on making PSCell ID available at the SGW of EPC | Huawei |
| R3-212066 | Discussion and conclusions on gNB-ID length exposure | Ericsson, Verizon, Bell Mobility |
| R3-212067 | Draft Reply LS on broadcasting gNB ID length in system information block | Ericsson, Verizon, Bell Mobility |
| R3-212071 | [DRAFT] Reply LS on information on the port number allocation solutions | Ericsson |
| R3-212072 | Port Number Allocation Solutions | Ericsson |
| R3-212082 | Discussion on Port Assignment for new interfaces | ZTE Corporation |
| R3-212094 | [DRAFT] Reply LS on RACS capability detection with S1 and NG handover | Ericsson |
| R3-212095 | On communication between source and target RAN node at CN handover for non-supported features | Ericsson |
| R3-212096 | Correcting assigned criticality for IEs in transparent handover containers | Ericsson |
| R3-212097 | Correcting assigned criticality for IEs in transparent handover containers | Ericsson |
| R3-212112 | NTN architecture aspects and cell ID mapping | Ericsson |
| R3-212113 | [DRAFT] [Reply] LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Ericsson |
| R3-212116 | IoT NTN Basic Architecture | Ericsson |
| R3-212117 | [DRAFT] [Reply] LS on IoT-NTN basic architecture | Ericsson |
| R3-212118 | Reply LS on QoS Monitoring for URLLC | Ericsson |
| R3-212146 | Time synchronization assistance parameters | Huawei |
| R3-212147 | [Draft] Reply LS on time synchronization assistance parameters | Huawei |
| R3-212148 | Discussion on E-RABs that cannot be handed over to 2G/3G | Huawei |
| R3-212149 | Discussion on E-RABs that cannot be handed over to 2G/3G | Huawei |
| R3-212150 | Expected UE Activity Behaviour | Huawei, Lenovo, Motorola Mobility |
| R3-212151 | Expected UE Activity Behaviour | Huawei, Lenovo, Motorola Mobility, Qualcomm Incorporated, ZTE |
| R3-212152 | User Plane Integrity Protection for eUTRA connected to EPC | Huawei |
| R3-212153 | [Draft] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Huawei |
| R3-212154 | RACS capability detection with S1 and NG handover | Huawei |
| R3-212155 | [Draft] Reply LS on RACS capability detection with S1 and NG handover | Huawei |
| R3-212171 | Discussion on conditional handover with SCG configuration | Huawei |
| R3-212172 | [Draft] Reply LS on on Conditional Handover with SCG configuration scenarios | Huawei |
| R3-212188 | Correction on Expected UE activity behaviour | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated, ZTE |
| R3-212199 | HO and/or reselection parameters ranges required by MLB | Huawei |
| R3-212200 | [draft] Reply LS on the clarification of HO and/or reselection parameters ranges required by MLB | Huawei |
| R3-212213 | Discussion on E-CID LTE measurements | Huawei |
| R3-212214 | [Draft] Reply LS on E-CID LTE measurement in Rel-15 | Huawei |
| R3-212215 | Discussion on Reply LS on IoT-NTN basic architecture | Huawei |
| R3-212217 | Discussion on E-CID LTE measurements | Huawei |
| R3-212223 | [Draft] Reply LS on E-CID LTE measurement in Rel-15 | Huawei |
| R3-212224 | Discussion on Reply LS on IoT-NTN basic architecture | Huawei |
| R3-212287 | Signaling support for UL packet delay distribution measurement in SA5 | Intel Corporation |
| R3-212288 | NGAP support for UL packet delay distribution measurement in SA5 | Intel Corporation |
| R3-212289 | E1AP support for UL packet delay distribution measurement in SA5 | Intel Corporation |
| R3-212290 | F1AP support for UL packet delay distribution measurement in SA5 | Intel Corporation |
| R3-212291 | NG-U support for UL packet delay distribution measurement in SA5 | Intel Corporation |
| R3-212292 | NR-U support for UL packet delay distribution measurement in SA5 | Intel Corporation |
| R3-212304 | Definition of Basic Handover | Ericsson |
| R3-212305 | Reply LS on Handover terminology | Ericsson |
| R3-212306 | Discussion on HO Terminology | Ericsson |
| R3-212307 | Reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Ericsson |
| R3-212308 | Discussion on L1/L2 inter cell mobility | Ericsson |
| R3-212309 | Reply LS on network sharing with multiple SSBs in a carrier | Ericsson |
| R3-212312 | Reply LS on the clarification of HO and/or reselection parameters ranges required by MLB | Ericsson |
| R3-212318 | Clarifications on OAM involvement in HO and Reselection parameters configuration for MLB | Ericsson |
| R3-212319 | Correction on handover and/or reselection configuration for MLB | Ericsson |
| R3-212334 | Discussion on PDU Session level "Expected UE activity behaviour" | Ericsson |
| R3-212335 | PDU Session level Expected UE activity behaviour | Ericsson |
| R3-212336 | Discussion on synchronization of Ethernet Compression | Ericsson |
| R3-212337 | Discussion on Time Synchronization assistance parameters | Ericsson |
| R3-212338 | Discussion on the RAN2 LS on E-CID LTE measurement in Rel-15 | Ericsson |
| R3-212339 | Reply LS on E-CID LTE measurement in Rel-15 | Ericsson |
| R3-212363 | User Plane Integrity Protection for eUTRA connected to EPC | Ericsson |
| R3-212364 | [DRAFT] Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Ericsson |
| R3-212365 | Conditional Handover with SCG configuration scenarios | Ericsson |
| R3-212366 | [DRAFT] Reply LS on Conditional Handover with SCG configuration scenarios | Ericsson |
| R3-212405 | Discussion on Conditional Handover with SCG configuration scenarios | Google Inc. |
| R3-212409 | [Draft] Reply LS on Conditional Handover with SCG configuration scenarios | Google Inc. |
| R3-212510 | Discussion on L1/L2-centric mobility | Huawei |
| R3-212511 | [Draft] Reply LS on L1/L2-centric mobility | Huawei |
| R3-212512 | Discussion on port no. allocation solutions | Huawei,Samsung |
| R3-212513 | [Draft] Reply LS on Information on the port number allocation solutions | Huawei |
| R3-212514 | Discussion on network sharing with multiple SSBs in a carrier | Huawei |
| R3-212562 | Reply LS on QoS Monitoring for URLLC(Response R3-211467) | ZTE |
| R3-212563 | PCR for 38.415:QoS Monitoring for URLLC(Response R3-211467) | ZTE |
| R3-212589 | LS on correction of round trip delay drift rate for NTN scenarios in TR38.821 | RAN WG1 |
| R3-212592 | [draft] Response LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Nokia, Nokia Shanghai Bell |
| R3-212594 | Reply LS on Granularity of the H/S/NA Slot Configurations for the IAB-DU | RAN1 |
| R3-212596 | LS on RACH procedure for HO with PSCell | RAN WG4 |
| R3-212600 | CB: # 2_PortNumberAllocation - Summary of email discussion | Huawei - moderator |
| R3-212601 | CB: # 3_L1-L2_Mobility - Summary of email discussion | Samsung - moderator |
| R3-212602 | CB: # 5_E-CID_LTEmeasurement - Summary of email discussion | Huawei - moderator |
| R3-212603 | CB: # 6_Flex_gNB_IDlength - Summary of email discussion | Ericsson - moderator |
| R3-212604 | CB: # 7_SNinitiated_SCGrelease - Summary of email discussion | Samsung - moderator |
| R3-212605 | CB: # 8_5GarchSatAccess - Summary of email discussion | Ericsson - moderator |
| R3-212606 | CB: # 9_IoT_NTNarch - Summary of email discussion | Huawei - moderator |
| R3-212607 | CB: # 10_CHO_SCGconfig - Summary of email discussion | Nokia - moderator |
| R3-212608 | CB: # 11_UPintegrityProtectionE-UTRA-EPC - Summary of email discussion | Qualcomm - moderator |
| R3-212609 | CB: # 12_EthernetCompSync - Summary of email discussion | Nokia - moderator |
| R3-212610 | CB: # 13_RACScapDetection_S1_NG_HO - Summary of email discussion | Ericsson - moderator |
| R3-212611 | CB: # 14_ExpUEActivBehavior - Summary of email discussion | Ericsson - moderator |
| R3-212612 | CB: # 15_E-RABSnoHOto2G_3G_5G - Summary of email discussion | Ericsson - moderator |
| R3-212613 | CB: # 16_HOterminology - Summary of email discussion | Nokia - moderator |
| R3-212614 | CB: # 17_QoSmonURLLC - Summary of email discussion | Huawei - moderator |
| R3-212615 | CB: # 18_HOreselParamRangesMLB - Summary of email discussion | Nokia - moderator |
| R3-212616 | CB: # 19_NWsharingMultiSSB - Summary of email discussion | Huawei - moderator |
| R3-212634 | Response to R3-212061, R3-212062, R3-212063 and R3-212064 | Ericsson |
| R3-212635 | Response to R3-211505, R3-211529, R3-211931, R3-212278 | NEC |
| R3-212647 | Response to R3-211616 and R3-211996 | Ericsson Inc. |
| R3-212727 | Response to R3-211616 and R3-211996 | Ericsson Inc. |
| R3-212800 | Reply LS to CT4 on Information on the port number allocation solutions | Huawei |
| R3-212802 | Reply LS on E-CID LTE measurement in Rel-15 measurements | Huawei |
| R3-212806 | Reply LS to LS on IoT-NTN basic architecture | Qualcomm Incorporated |
| R3-212808 | Expected UE Activity Behaviour | Huawei, Lenovo, Motorola Mobility, Qualcomm Incorporated, ZTE |
| R3-212809 | Correction on Expected UE activity behaviour | Lenovo, Motorola Mobility, Huawei, Qualcomm Incorporated, ZTE |
| R3-212812 | Reply LS to LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R3-212840 | Reply LS on Draft Reply LS on the clarification of HO and/or reselection parameters ranges required by MLB | Huawei |
| R3-212847 | Enabling CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-212848 | Response LS on Conditional Handover with SCG configuration scenarios | Nokia, Nokia Shanghai Bell |
| R3-212879 | Reply LS to RAN1 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Samsung |
| R3-212884 | [DRAFT] [Reply] LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Ericsson |
| R3-212905 | Reply LS on LS Reply on QoS Monitoring for URLLC | Huawei |
| R3-212907 | Response LS on Handover terminology | Nokia, Nokia Shanghai Bell |
| R3-212916 | Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G | Ericsson |
| R3-212922 | Enabling CHO with SCG configuration | Nokia, Nokia Shanghai Bell |
| R3-212937 | Reply LS on LS Reply on QoS Monitoring for URLLC | Huawei |
| R3-212941 | Draft Reply LS on broadcasting gNB ID length in system information block | Ericsson, Verizon, Bell Mobility |
| R3-212942 | Reply LS on broadcasting gNB ID length in system information block | Ericsson, Verizon, Bell Mobility |
| R3-212966 | Reply LS on broadcasting gNB ID length in system information block | Ericsson, Verizon, Bell Mobility |
| 8.3.3 | SRS-RSRP Information Exchange | |
| R3-212564 | Left issue for CLI | ZTE |
| R3-212565 | CLI Notification between NG-RAN node | ZTE |
| R3-212566 | Response LS on SRS-RSRP | ZTE |
| R3-212617 | CB: # 21_SRS-SRSPinfoXchg - Summary of email discussion | ZTE - moderator |
| R3-212889 | Response LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI | ZTE |
| 9.2.1 | RAT Type Handling | |
| R3-211534 | Consideration on the Supported RAT of the CN | Huawei |
| R3-211535 | Supported RATs of the AMF | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless, Orange |
| R3-211536 | Supported RATs of the MME | Huawei, CMCC, Vodafone, Telecom Italia, China Telecom, Deutsche Telekom, China Unicom, Verizon Wireless, Orange |
| R3-212340 | Closing the remaining aspect of RAT type handling discussion | Ericsson |
| R3-212618 | CB: # 22_RATtypeHandling - Summary of email discussion | Huawei - moderator |
| 9.2.2 | DRX Information Delivery for RRC_INACTIVE | |
| R3-211537 | Consideration on paging DRX in XnAP RAN Paging | Huawei |
| R3-211538 | Correction on Paging DRX in RAN PAGING message | Huawei |
| R3-211539 | Consideration on providing eDRX information in XnAP RAN Paging | Huawei |
| R3-211540 | RAN Paging Optimization | Huawei |
| R3-211591 | Discussion on the UE information delivery for RRC_INACTIVE UE | ZTE, Qualcomm Incorporated, Ericsson, Nokia,Nokia Shanghai Bell |
| R3-211592 | 38.423(Rel-15) UE specific DRX delivery for NR and eLTE | ZTE,Qualcomm Incorporated,Nokia,Nokia Shanghai Bell, Ericsson |
| R3-211593 | 38.423(Rel-16) Correction on the DRX information delivery for RRC_INACTIVE UE in XnAP | ZTE, Qualcomm Incorporated, Ericsson, Nokia,Nokia Shanghai Bell |
| R3-211594 | 38.473(Rel-15) UE information delivery in F1AP PAGING for NR | ZTE, Qualcomm Incorporated,Nokia,Nokia Shanghai Bell, Ericsson |
| R3-211595 | 38.473(Rel-16) UE information delivery in F1AP PAGING for NR | ZTE, Qualcomm Incorporated,Nokia,Nokia Shanghai Bell, Ericsson |
| R3-212597 | Response to R3-211591 | Huawei |
| R3-212598 | Response to R3-211591 | Huawei |
| R3-212619 | CB: # 23_DRXinfoRRC_INACTIVE - Summary of email discussion | ZTE - moderator |
| R3-212810 | UE specific DRX delivery | ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-212811 | Paging eDRX information delivery for RRC_INACTIVE UE in XnAP | Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Ericsson, Huawei |
| R3-212821 | UE specific DRX delivery | ZTE,Qualcomm Incorporated,Nokia,Nokia Shanghai Bell, Ericsson |
| R3-212925 | CB: # 23_DRXinfoRRC_INACTIVE - Summary of email discussion | ZTE - moderator |
| R3-212926 | UE specific DRX delivery | ZTE, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-212930 | Paging eDRX information delivery for RRC_INACTIVE UE in XnAP | Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Ericsson, Huawei |
| R3-212999 | UE specific DRX delivery | ZTE, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| 9.2.3 | IMS Voice EPS Fallback | |
| R3-211637 | Correction of IMS voice EPS fallback | Nokia, Nokia Shanghai Bell |
| R3-211638 | Correction of IMS voice EPS fallback | Nokia, Nokia Shanghai Bell |
| R3-212329 | Discussion on IMS Voice EPS Fallback | Ericsson |
| R3-212330 | Correction of IMS voice EPS fallback from 5G | Ericsson |
| R3-212331 | Correction of IMS voice EPS fallback from 5G | Ericsson |
| R3-212332 | Introduce the IMS voice EPS fallback from 5G in the Retrieve UE Context procedure | Ericsson |
| R3-212333 | Introduce the IMS voice EPS fallback from 5G in the Retrieve UE Context procedure | Ericsson |
| R3-212456 | Discussion on IMS voice EPS fallback | Huawei |
| R3-212457 | Discussion on IMS voice EPS fallback | Huawei |
| R3-212620 | CB: # 24_IMSvoiceEPS_fb - Summary of email discussion | Nokia - moderator |
| R3-212814 | Correction of IMS voice EPS fallback | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-212857 | Correction of IMS voice EPS fallback from 5G | Ericsson, Nokia, Nokia Shanghai Bell |
| 9.2.4 | Others | |
| R3-212273 | Correction on LTE aerial feature | Ericsson, Qualcomm Incorporated |
| R3-212274 | Correction on LTE aerial feature | Ericsson, Qualcomm Incorporated |
| R3-212433 | Correction on Extended UE Identity Index Value | Huawei |
| R3-212552 | Addition of User location Information to NG-AP Suspend Request | Ericsson |
| R3-212728 | Correction on LTE aerial feature | Ericsson, Qualcomm Incorporated |
| R3-212729 | Correction on Extended UE Identity Index Value | Huawei |
| R3-212963 | Correction on Extended UE Identity Index Value | Huawei |
| 9.3.1 | NAS Non-Delivery | |
| R3-211457 | Reply LS on Reply LS on NAS Non delivery for RRC Inactive state | SA2 |
| R3-211639 | Correction of NAS PDU Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-211640 | Correction of NAS PDU Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-211641 | Reply LS on NAS Non delivery for RRC Inactive state | Nokia, Nokia Shanghai Bell |
| R3-211772 | NAS PDU non delivery | Ericsson |
| R3-211773 | NAS PDU handling | Ericsson |
| R3-211774 | NAS PDU handling | Ericsson |
| R3-211775 | NAS PDU handling | Ericsson |
| R3-211776 | NAS PDU handling | Ericsson |
| R3-211810 | Further discussion on NAS Non Delivery | CATT |
| R3-211811 | Correction to NAS Non Delivery Indication_fb0 | CATT |
| R3-211812 | Correction to NAS Non Delivery Indication_g50 | CATT |
| R3-211859 | Discussion on NAS non delivery | ZTE Corporation |
| R3-211860 | Correction on NAS non delivery for R15 | ZTE Corporation |
| R3-211871 | Correction on NAS non delivery for R16 | ZTE Corporation |
| R3-211922 | NAS Non-Delivery | Huawei |
| R3-211923 | NAS Non-Delivery | Huawei |
| R3-211924 | NAS Non-Delivery | Huawei |
| R3-211925 | [Draft] Reply LS on NAS Non-Delivery | Huawei |
| R3-212621 | CB: # 25_NASnonDelivery - Summary of email discussion | CATT - moderator |
| R3-212881 | Correction on NAS non delivery for R16 | ZTE |
| R3-212892 | NAS PDU handling | Ericsson |
| R3-212893 | Correction of NAS PDU Non Delivery | Nokia, Nokia Shanghai Bell, Orange |
| R3-212894 | NAS Non-Delivery | Huawei |
| 9.3.2 | RAN Sharing Enhancement for MLB | |
| R3-212119 | RAN Sharing enhancement for MLB | Ericsson |
| R3-212462 | Further Discussion on RAN Sharing Enhancement for MLB | ZTE, China Telecom, China Unicom |
| R3-212463 | CR for TS38.300 on RAN Sharing Enhancement for MLB | ZTE, China Telecom, China Unicom |
| R3-212464 | CR for TS 38.423 on Resource Status Reporting for RAN Sharing | ZTE, China Telecom, China Unicom |
| R3-212467 | CR for TS38.423 on Mobility Setting Change for RAN Sharing | ZTE, China Telecom, China Unicom |
| R3-212622 | CB: # 26_RANsharingMLB - Summary of email discussion | ZTE - moderator |
| 9.3.3 | NR-NR DC Configuration Release | |
| R3-211406 | Discussion on SCG addition and removal in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-211407 | SCG Event Indication over F1 | Nokia, Nokia Shanghai Bell |
| R3-211428 | LS on signalling SN initiated release of SCG | RAN2 |
| R3-211505 | Consideration on SN-initiated SCG release | Nokia, Nokia Shanghai Bell |
| R3-211506 | Response LS on signalling SN initiated release of SCG | Nokia, Nokia Shanghai Bell |
| R3-211529 | Consideration on signalling SN initiated release of SCG | Huawei |
| R3-211530 | [DRAFT] Reply LS on signalling SN initiated release of SCG | Huawei |
| R3-211531 | Information about SCG Release from MN-gNB-CU to MN-gNB-DU | Huawei |
| R3-211575 | Discussion on NR-NR DC Configuration Release | ZTE |
| R3-211576 | R15CR37.340 for SCG release | ZTE |
| R3-211577 | R16CR37.340 for SCG release | ZTE |
| R3-211578 | R15CR38.423 for SCG release | ZTE |
| R3-211579 | R16CR38.423 for SCG release | ZTE |
| R3-211580 | [DRAFT] Reply LS on signalling SN initiated release of SCG | ZTE |
| R3-211931 | Discussion on SCG release over Xn | Samsung |
| R3-211932 | Stage-3 CR on SCG release over Xn (Rel-15) | Samsung |
| R3-211933 | Stage-3 CR on SCG release over Xn (Rel-16) | Samsung |
| R3-211934 | [Draft] Reply LS on signaling SN initiated release of SCG | Samsung |
| R3-211935 | Discussion on SCG release over F1 | Samsung |
| R3-211936 | Stage-3 CR on SCG release over F1 (Rel-15) | Samsung |
| R3-211937 | Stage-3 CR on SCG release over F1 (Rel-16) | Samsung |
| R3-211938 | Stage-3 CR on SCG release over W1 (Rel-16) | Samsung |
| R3-212278 | Reply LS on signalling SN initiated release of SCG | Ericsson |
| R3-212279 | How to release SCG configuration between MN-CU and MN-DU | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212280 | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212281 | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212553 | How to release SCG configuration between MN and SN in stage-2 | Ericsson |
| R3-212554 | How to release SCG configuration between MN and SN in stage-2 | Ericsson |
| R3-212555 | How to release SCG configuration between MN and SN CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212556 | How to release SCG configuration between MN and SN CR 36.423 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212557 | How to release SCG configuration between MN and SN CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212558 | How to release SCG configuration between MN and SN CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212623 | CB: # 27_NR-NR_DCconfigRelease - Summary of email discussion | Ericsson - moderator |
| R3-212910 | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212911 | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212912 | How to release SCG configuration between MN and SN CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212913 | How to release SCG configuration between MN and SN CR 38.423 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212918 | R15CR37.340 for SCG release | ZTE, Ericsson |
| R3-212919 | R16CR37.340 for SCG release | ZTE, Ericsson |
| R3-212920 | Stage-3 CR on SCG release over W1 (Rel-16) | Samsung |
| R3-212932 | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212949 | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212950 | How to release SCG configuration between MN-CU and MN-DU CR 38.473 | Ericsson, Verizon Wireless, Deutsche Telekom, Telecom Italia |
| R3-212955 | Stage-3 CR on SCG release over W1 (Rel-16) | Samsung |
| 9.3.4.1 | E1 Aspects | |
| R3-211642 | Support of 4g-5g direct data forwarding over E1 | Nokia, Nokia Shanghai Bell |
| R3-211643 | Support of 4g-5g direct data forwarding over E1 | Nokia, Nokia Shanghai Bell |
| R3-211825 | Support of direct data forwarding for inter-system handover w/o shared gNB | CATT, China Telecom, ZTE |
| R3-211826 | Support of inter-node handover with a shared split (S) gNB | CATT, China Telecom, ZTE |
| R3-211957 | Direct data forwarding for inter-system HO from 4G to 5G | Samsung, LGU+, Huawei |
| R3-211958 | Support of direct data forwarding for inter-system HO from 4G to 5G | Samsung, LGU+, Huawei |
| R3-212356 | E1 aspects of inter-system direct data forwarding | Ericsson |
| R3-212400 | Direct data forwarding for 5G to 4G handover | Huawei, Samsung |
| R3-212406 | Support of direct data forwarding for inter-system HO | China Telecom, CATT, ZTE |
| R3-212545 | Direct data forwarding for 5G to 4G handover | Huawei, Samsung |
| R3-212624 | CB: # 28_DirectDataFwd_E1aspects - Summary of email discussion | Samsung - moderator |
| R3-212813 | Support of 4g-5g direct data forwarding over E1 | Nokia, Nokia Shanghai Bell |
| 9.3.4.2 | With Mobility Between DC and SA | |
| R3-211744 | S-node direct data forwarding in handover between NSA and SA | Qualcomm Incorporated, CATT, China Telecom |
| R3-211745 | SN direct data forwarding | Qualcomm Incorporated, CATT |
| R3-211746 | SN direct data forwarding | Qualcomm Incorporated, CATT |
| R3-211954 | Direct data forwarding for mobility between DC and SA | Samsung, Huawei |
| R3-212458 | Direct data forwarding for mobility between DC and SA | Huawei, Samsung |
| R3-212625 | CB: # 29_DirectDataFwd_DC-SAmobility - Summary of email discussion | Qualcomm - moderator |
| R3-212748 | SN direct data forwarding | Qualcomm Incorporated, CATT |
| 9.3.4.3 | PDCP SN Handling for EPC to 5GC HO | |
| R3-211516 | Next steps for direct data forwarding from EN-DC to NR SA | Nokia, Nokia Shanghai Bell |
| R3-211955 | PDCP SN Handling for EPC to 5GC HO | Samsung |
| R3-211956 | PDCP SN Handling and IP address selection for EPC to 5GC HO | Samsung |
| R3-212357 | PDCP SNs for forwarded PDCP SDUs from 4G to 5G | Ericsson |
| R3-212369 | Inter-system indicator for Bearer Context Setup | Ericsson |
| R3-212459 | PDCP SN issue for EPC to 5GC handover | Huawei |
| R3-212626 | CB: # 30_DirectDataFwd_PDCP_SNhandling_EPC-5GC_HO - Summary of email discussion | Ericsson - moderator |
| R3-212927 | Inter-system indicator for Bearer Context Setup | Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei |
| R3-212928 | CB: # 30_DirectDataFwd_PDCP_SNhandling_EPC-5GC_HO - Summary of email discussion | Ericsson - moderator |
| 9.3.6 | Lossless Intra-System HO in CP-UP Separation Scenario | |
| R3-211408 | Discussion on Lossless intra-system HO in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-211409 | Lossless intra-system HO in disaggregated architecture | Nokia, Nokia Shanghai Bell |
| R3-211947 | Lossless intra-system HO in dis-aggregated gNB scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+ |
| R3-211948 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+ |
| R3-211949 | Correction of intra-system HO in CP-UP separation scenario | Samsung, Huawei, Intel Corporation, China Telecom, LGU+ |
| R3-212360 | Lossless Intra-System HO in CP-UP Separation Scenario | Ericsson |
| R3-212627 | CB: # 31_LosslessIntraSysHO_CP-UPsplit - Summary of email discussion | Samsung - moderator |
| 9.3.7 | Mobility Restrictions in SN Addition | |
| R3-211522 | Consideration on Mobility Restriction in SN addition | Huawei |
| R3-211523 | Correction on the RAT Restriction Information | Huawei |
| R3-211524 | Correction on the RAT Restriction Information | Huawei |
| R3-211525 | Introduce 5GC Mobility Restriction List Container in DC | Huawei, Qualcomm Incorporated |
| R3-211526 | Introduce 5GC Mobility Restriction List Container in DC | Huawei, Qualcomm Incorporated |
| R3-211527 | Introduce EPC Handover Restriction List Container in EN-DC | Huawei, Qualcomm Incorporated |
| R3-211528 | Introduce EPC Handover Restriction List Container in EN-DC | Huawei, Qualcomm Incorporated |
| R3-211608 | Mobility Restrictions in S-Node Addition | Nokia, Nokia Shanghai Bell |
| R3-211609 | Clarification of 5GC Mobility Restriction List Container | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211610 | Clarification of EPC Handover Restriction List Container | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211611 | Correction to RAT Restriction Information IE in the Mobility Restriction List | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211612 | Correction to RAT Restriction Information IE in the Mobility Restriction List | Nokia, Nokia Shanghai Bell, Ericsson |
| R3-211781 | Mobility Restrictions in SN Addition | Qualcomm Incorporated |
| R3-211782 | Introduce 5GC Mobility Restriction List Container in DC | Qualcomm Incorporated, Huawei |
| R3-212098 | Necessary corrections on the usage of the 5GC MRL Container IE on Xn | Ericsson |
| R3-212129 | Introduce 5GC Mobility Retriction List Container in DC | Qualcomm Incorporated, Huawei |
| R3-212628 | CB: # 32_MobRestr_SNadd - Summary of email discussion | Nokia - moderator |
| R3-212830 | Correction on the RAT Restriction Information | Huawei, Nokia, Nokia Shanghai-Bell |
| R3-212831 | Correction on the RAT Restriction Information | Huawei, Nokia, Nokia Shanghai-Bell |
| R3-212871 | Mobility Restriction List handling in MR-DC with 5GC | Qualcomm Incorporated, Huawei |
| 9.3.8.1 | Other Corrections | |
| R3-211403 | Discussion on Serving Cell Information from gNB-DU | Nokia, Nokia Shanghai Bell, ZTE |
| R3-211404 | Serving Cell Information from gNB-DU | Nokia, Nokia Shanghai Bell, ZTE |
| R3-211405 | Private Message Definition | Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-211503 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-211504 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-211532 | Consideration on EN-DC Resource Status Reporting | Huawei, Qualcomm Incorporated, BT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-211533 | Correction of en-gNB initiated EN-DC Resource Status Reporting | Huawei, Qualcomm Incorporated, BT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-211606 | Correction of Spatial Relation Information | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Qualcomm Incorporated |
| R3-211607 | Correction of Spatial Relation Information | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Qualcomm Incorporated |
| R3-211621 | Use of the UE’s Radio Capability for Paging in RRC_INACTIVE | Qualcomm Incorporated, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics |
| R3-211622 | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | Qualcomm Incorporated, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics |
| R3-211623 | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | Qualcomm Incorporated, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics |
| R3-211644 | Correction of PDU Session Modify | Nokia, Nokia Shanghai Bell, Orange |
| R3-211645 | Correction of MICO mode | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Deutsche Telekom |
| R3-211646 | Correction of MICO mode | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Deutsche Telekom |
| R3-211647 | Correction of PDU Type Frame | Nokia, Nokia Shanghai Bell, Orange |
| R3-211648 | Correction of PDU Type Frame | Nokia, Nokia Shanghai Bell, Orange |
| R3-211667 | Correction of NG Handover | Nokia, Nokia Shanghai Bell |
| R3-211668 | Correction of NG Handover | Nokia, Nokia Shanghai Bell |
| R3-211670 | Correction of PDU Session Container | NEC |
| R3-211671 | Correction of PDU Session Container | NEC |
| R3-211673 | Correction on reference to RACH-Report | NEC |
| R3-211694 | Discussion on E1AP handling for unmapped flows in DL | CATT,Intel Corporation,Huawei,China Telecom |
| R3-211695 | CR on E1AP handling for unmapped DL QoS flows | CATT, Intel Corporation,Huawei, China Telecom |
| R3-211696 | CR on E1AP handling for unmapped DL QoS flows | CATT, Intel Corporation,Huawei, China Telecom |
| R3-211697 | Correction on MRO related issues | CATT |
| R3-211698 | Discussion on multiple Trace Session activations | CATT, Huawei, China Telecom |
| R3-211699 | Clarification on multiple Trace Start procedure | CATT, Huawei, China Telecom |
| R3-211700 | Clarification on multiple Trace Start procedure | CATT, Huawei, China Telecom |
| R3-211711 | RACH Report Container(CR to 38423) | China Telecommunication |
| R3-211712 | RACH Report Container(CR to 38473) | China Telecommunication |
| R3-211721 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-211722 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-211723 | Clarification on TAI Slice Support List | China Telecommunication |
| R3-211730 | Correction on Signalling based MDT Activation [NR_SON_MDT-Core] | ZTE, China Telecom, Samsung |
| R3-211747 | Inter MN resume without SN change | Qualcomm Incorporated, China Telecom, T-Mobile USA |
| R3-211748 | Inter MN resume without SN change (CR to 38.423) | Qualcomm Incorporated, China Telecom, T-Mobile USA |
| R3-211749 | Remaining BSR transfer in handover | Qualcomm Incorporated, China Telecom, T-Mobile USA |
| R3-211750 | Remaining BSR transfer in handover | Qualcomm Incorporated, China Telecom, T-Mobile USA |
| R3-211763 | MRO Inter-system measurement Configuration | Ericsson |
| R3-211764 | MRO S1AP clarifications for Inter-system measurement Configuration | Ericsson |
| R3-211765 | Maximum Number of RRC connections | Ericsson, CMCC |
| R3-211769 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-211770 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-211771 | Handling PDCP Duplication | Ericsson, Intel Corporation |
| R3-211794 | Correction on Abnormal Conditions in Handover Preparation Procedure for R15 | CATT, Huawei |
| R3-211795 | Correction on Abnormal Conditions in Handover Preparation Procedure for R16 | CATT, Huawei |
| R3-211796 | Discussion on removing the restriction of cause value of “procedure cancelled” | CATT |
| R3-211797 | Remove the restriction on cause value “procedure cancelled” for 38.423 (R15) | CATT |
| R3-211798 | Remove the restriction on cause value “procedure cancelled” for 38.423 (R16) | CATT |
| R3-211813 | Including Mobility Restriction List in PATH SWITCH REQUEST ACKNOWLEDGE_v15 | CATT |
| R3-211814 | Including Mobility Restriction List in PATH SWITCH REQUEST ACKNOWLEDGE_v16 | CATT |
| R3-211824 | Editorial corrections on IE type and reference in tabular for TS38.423 | ZTE Corporation |
| R3-211827 | Correction CR on Network instance for 38.413(R15) | CATT |
| R3-211828 | Correction CR on Network instance for 38.413(R16) | CATT |
| R3-211829 | CR to TS 38463 for Intra gNB-CU-UP DAPS HO | CATT |
| R3-211857 | Correction on detection mechanisms for Intra-system too late handover | CATT,CMCC,ZTE |
| R3-211878 | Discussion on Reflective QoS Attribute | ZTE, China Unicom, China Telecom, CMCC |
| R3-211879 | Reflective QoS Attribute over NG for R15 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211880 | Reflective QoS Attribute over NG for R16 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211881 | Reflective QoS Attribute over Xn for R15 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211882 | Reflective QoS Attribute over Xn for R16 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211883 | Reflective QoS Attribute over F1 for R15 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211884 | Reflective QoS Attribute over F1 for R16 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211885 | Reflective QoS Attribute over E1 for R15 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211886 | Reflective QoS Attribute over E1 for R16 | ZTE,China Unicom, China Telecom, CMCC |
| R3-211926 | Clarification on SIB and System information message over F1 | Samsung, ZTE, NEC, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei |
| R3-211927 | Stage-2 CR on system information message over F1 (Rel-15) | Samsung, ZTE, NEC, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei |
| R3-211928 | Stage-3 CR on system information message over F1 (Rel-15) | Samsung, ZTE, NEC, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei |
| R3-211929 | Stage-2 CR on system information message over F1 (Rel-16) | Samsung, ZTE, NEC, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei |
| R3-211930 | Stage-3 CR on system information message over F1 (Rel-16) | Samsung, ZTE, NEC, Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei |
| R3-211950 | Issue in RESOURCE STATUS REQUEST message | Samsung, CMCC, ZTE, CATT, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R3-211951 | Correction of ASN.1 definition for RESOURCE STATUS REQUEST messageand semantics for Resource Status Reporting Initiation procedure | Samsung, CMCC, ZTE, CATT, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R3-211952 | Issues in stage 2 on MRO | Samsung, CMCC, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-211953 | Correction of MRO in stage 2 | Samsung, CMCC, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Lenovo, Motorola Mobility |
| R3-211993 | Correction for UL Data Notification over E1 | Huawei, Intel Corporation, CATT, China Telecom |
| R3-211994 | Correction for UL Data Notification over E1 | Huawei, Intel Corporation, CATT, China Telecom |
| R3-211995 | Correction for UL Data Notification over E1 | Huawei, Intel Corporation, CATT, China Telecom |
| R3-212004 | Introduction of reporting frequency to F1AP for Qos monitoring for URLLC | Huawei, China Telecom, Samsung, CATT, Nokia, Nokia Shanghai Bell, CMCC |
| R3-212005 | Introduction of reporting frequency to F1AP for Qos monitoring for URLLC | Huawei, China Telecom, Samsung, CATT, Nokia, Nokia Shanghai Bell |
| R3-212006 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-212007 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-212008 | Support of dynamic ACL during handover and dual connectivity | Huawei, Deutsche Telekom, China Telecom |
| R3-212009 | Correction on release-with-redirect in 2-step RRC resume procedure | Huawei, China Unicom |
| R3-212010 | Correction on release-with-redirect in 2-step RRC resume procedure | Huawei, China Unicom |
| R3-212016 | Correction on missing IE of EHC | Huawei, China Unicom |
| R3-212017 | Direct forwarding path availability in Handover Required message | Huawei, CATT, Nokia, Nokia Shanghai Bell, China Unicom |
| R3-212018 | Direct forwarding path availability in Handover Required message | Huawei, CATT, Nokia, Nokia Shanghai Bell, China Unicom |
| R3-212021 | CR to 37.473 on MeasGapSharingConfig | Huawei, China Unicom |
| R3-212035 | Max number of F1-C links is exceeded at CU | Ericsson, Verizon Wireless |
| R3-212036 | Max number of F1-C links is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless |
| R3-212043 | Max number of F1-C links is exceeded at CU CR 38.473 | Ericsson, Verizon Wireless |
| R3-212054 | Correction for NPN related Served Cell Information (Option 1) [NG_RAN_PRN-Core] | ZTE Corporation |
| R3-212055 | Correction for NPN related Served Cell Information (Option 2) [NG_RAN_PRN-Core] | ZTE Corporation |
| R3-212058 | Correction on SRB ID | Huawei, CATT, CMCC |
| R3-212059 | Correction on SRB ID | Huawei, CATT, CMCC |
| R3-212068 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson, NTT DOCOMO, Deutsche Telekom,Verizon Wireless, |
| R3-212069 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson, NTT DOCOMO, Deutsche Telekom,Verizon Wireless, |
| R3-212073 | Cause value on S1 and NG for insufficient UE capabilities | Ericsson, Deutsche Telekom |
| R3-212074 | Cause value on S1AP for insufficient UE capabilities CR 36.413 | Ericsson, Deutsche Telekom |
| R3-212075 | Cause value on S1AP for insufficient UE capabilities CR 36.413 | Ericsson, Deutsche Telekom |
| R3-212076 | Cause value on NGAP for insufficient UE capabilities CR 38.413 | Ericsson, Deutsche Telekom |
| R3-212077 | Cause value on NGAP for insufficient UE capabilities CR 38.413 | Ericsson, Deutsche Telekom |
| R3-212084 | Support of shared-DU and dedicated logical-CU for NPN | Huawei, China Telecom, Orange |
| R3-212085 | Correction of Allocated C-RNTI for 2-step RACH | Huawei, CMCC |
| R3-212086 | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | Huawei, CMCC, Orange, Deutsche Telekom |
| R3-212087 | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | Huawei, CMCC, Orange, Deutsche Telekom |
| R3-212088 | Interactions with other procedures for the UE TNLA BINDING RELEASE | Huawei, China Telecom, Orange |
| R3-212089 | Interactions with other procedures for the UE TNLA BINDING RELEASE | Huawei, China Telecom, Orange |
| R3-212090 | Clarification on NPN Mobility Information in Mobility Restriction List | Huawei, China Telecom |
| R3-212091 | Clarification on NPN Mobility Information in Mobility Restriction List | Huawei, China Telecom |
| R3-212173 | Miscellaneous corrections on IAB in TS 38.473 | ZTE |
| R3-212216 | Correction on SFN Initialization time | Huawei, Qualcomm Incorporated |
| R3-212218 | Correction on relative cartesian coordinate | Huawei, Qualcomm Incorporated, Ericsson, Nokia |
| R3-212219 | Correction on relative cartesian coordinate | Huawei, Qualcomm Incorporated, Ericsson, Nokia |
| R3-212232 | Correction on SFN Initialization time | Huawei, Qualcomm Incorporated |
| R3-212233 | Correction on SFN Initialization time | Huawei, Qualcomm Incorporated |
| R3-212234 | Correction on relative cartesian coordinate | Huawei, Qualcomm Incorporated, Ericsson, Nokia |
| R3-212235 | Correction on relative cartesian coordinate | Huawei, Qualcomm Incorporated, Ericsson, Nokia |
| R3-212236 | Discussion on NRPPa transaction types | Huawei, CMCC |
| R3-212270 | Correction of maximum extended slice support items | NTT DOCOMO INC. |
| R3-212272 | Correction of inter system SON configuration Transfer | NTT DOCOMO INC. |
| R3-212275 | Resolve conflicts in the SN initiated SN modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC. |
| R3-212276 | Correction on SN initiated SN Modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC. |
| R3-212277 | Correction on SN initiated SN Modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC. |
| R3-212282 | Correction for CHO early data forwarding in MN to eNB/gNB Change | Intel Corporation, Samsung, LGE, Lenovo, Motorola Mobility |
| R3-212283 | 36.423 correction for CHO early data forwarding in MN to eNB Change scenario | Intel Corporation, Samsung, LGE |
| R3-212284 | 38.423 correction for CHO early data forwarding in MN to ng-eNB/gNB Change | Intel Corporation, Samsung, LGE |
| R3-212285 | 36.300 correction for CHO early data forwarding in MeNB to eNB Change scenario | Intel Corporation, Samsung, LGE |
| R3-212286 | 37.340 correction for CHO early data forwarding in MN to eNB/gNB Change scenario | Intel Corporation, Samsung, LGE |
| R3-212295 | X2AP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-212296 | XnAP SN Status Transfer description correction for RLC-UM configured with DAPS | Intel Corporation |
| R3-212320 | Correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell |
| R3-212321 | Correction for multi-PLMN deployments | Nokia, Nokia Shanghai Bell |
| R3-212341 | Correction on the use of the Core Network Assistance Information for RRC INACTIVE IE | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE |
| R3-212342 | Clarification on the specified maximum length of the Routing ID Octet String | Ericsson |
| R3-212343 | Discussion on the need of sidelink resource allocation coordination between NG-RAN nodes for NR V2X | Ericsson, LG Electronics, LGU+, Deutsche Telekom, CATT, NTT Docomo, InterDigital, Intel Corporation |
| R3-212344 | Addition of sidelink MR-DC resource coordination | Ericsson, LG Electronics, LGU+, Deutsche Telekom, CATT, NTT Docomo, InterDigital, Intel Corporation |
| R3-212345 | Addition of MeNB to SN sidelink resource coordination | Ericsson, LG Electronics, LGU+, Deutsche Telekom, CATT, NTT Docomo, InterDigital, Intel Corporation |
| R3-212367 | UL primary path signaling over E1 | Ericsson |
| R3-212368 | UL primary path signaling over E1 | Ericsson |
| R3-212382 | Discussion on max number of NR-CGI over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung |
| R3-212383 | Maximum number of NRCGI over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung |
| R3-212387 | LTE-NR timing without GNSS | China Telecom, Qualcomm Incorporated |
| R3-212410 | Correction on BH RLC CH configured for BAP control PDU | Huawei, CATT, Qualcomm , Lenovo, Motorola Mobility,Nokia, Nokia Shanghai Bell |
| R3-212411 | Correction on gNB-DU Resource Configuration | Huawei, China Unicom |
| R3-212412 | Correction on UL BH information configuration for DRBs support CA based duplication | Huawei, Qualcomm, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R3-212460 | Correction on SFN Initialization time | Huawei, Qualcomm Incorporated, CMCC |
| R3-212461 | Correction on SFN Initialization time | Huawei, Qualcomm Incorporated, CMCC |
| R3-212509 | Correction on LTE UE RLF Report | China Telecom,CATT |
| R3-212535 | Issue of HARQ-related parameters in Assistance Information | Samsung |
| R3-212536 | Issue of HARQ-related parameters in Assistance Information | Samsung |
| R3-212539 | Correction of the DAPS Response Information IE in the tabular | Samsung, Ericsson, Intel Corporation, CATT |
| R3-212547 | Correction for shared SgNB/gNB case | Huawei, China Unicom |
| R3-212548 | Correction for shared SgNB/gNB case | Huawei, China Unicom |
| R3-212549 | Correction for shared SgNB/gNB case | Huawei, China Unicom |
| R3-212550 | Assistance information for UL duplication | Huawei, China Unicom |
| R3-212551 | Correction of last PDU session release for SSC mode 2 | Huawei, China Telecom |
| R3-212559 | Support of Aerial feature | Ericsson, Qualcomm Incorporated, Intel Corporation, NTT DOCOMO, INC. |
| R3-212560 | Introduction of Aerial authorization information | Ericsson, Qualcomm Incorporated, Intel Corporation, NTT DOCOMO, INC. |
| R3-212561 | Introduction of Aerial authorization information | Ericsson, Qualcomm Incorporated, Intel Corporation, NTT DOCOMO, INC. |
| R3-212567 | NGAP cause value for UE context transfer_R15 | ZTE,China Telecom |
| R3-212568 | NGAP cause value for UE context transfer_R16 | ZTE,China Telecom |
| R3-212569 | Introduce Masked IMEISV in E1AP R15 | ZTE,China Unicom,China Telecom |
| R3-212570 | Introduce Masked IMEISV in E1AP R16 | ZTE,China Unicom,China Telecom |
| R3-212578 | Correction on RAN Sharing over F1 for R15 | ZTE, China Telecom, China Unicom |
| R3-212579 | Correction on RAN Sharing over F1 for R16 | ZTE, China Telecom, China Unicom |
| R3-212580 | Correction on MLB for TS38.473 [NR_SON_MDT-Core] | ZTE, China Telecom, China Unicom |
| R3-212654 | CB: # 105_Rel-16Corr_SONMDT - Summary of email discussion | CMCC - moderator |
| R3-212655 | CB: # 106_Rel-16Corr_Positioning - Summary of email discussion | Nokia - moderator |
| R3-212656 | CB: # 107_Rel-16Corr_IAB - Summary of email discussion | Qualcomm - moderator |
| R3-212716 | Support of Aerial feature | Ericsson, Qualcomm Incorporated, Intel Corporation, NTT DOCOMO, INC., AT&T, Verizon Wireless |
| R3-212717 | Introduction of Aerial authorization information | Ericsson, Qualcomm Incorporated, Intel Corporation, NTT DOCOMO, INC., AT&T, Verizon Wireless |
| R3-212718 | Introduction of Aerial authorization information | Ericsson, Qualcomm Incorporated, Intel Corporation, NTT DOCOMO, INC., AT&T, Verizon Wireless |
| R3-212720 | Issue in RESOURCE STATUS REQUEST message | Samsung, CMCC, ZTE, CATT, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Verizon, Ericssion |
| R3-212721 | Correction of ASN.1 definition for RESOURCE STATUS REQUEST messageand semantics for Resource Status Reporting Initiation procedure | Samsung, CMCC, ZTE, CATT, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Verizon, Ericssion |
| R3-212730 | CB: # 108_SL_MR-DCresCoord - Summary of email discussion | Ericsson - moderator |
| R3-212731 | Addition of sidelink MR-DC resource coordination | Ericsson, LG Electronics, LGU+, Deutsche Telekom, CATT, NTT Docomo, InterDigital, Intel Corporation, Huawei |
| R3-212732 | Addition of MeNB to SN sidelink resource coordination | Ericsson, LG Electronics, LGU+, Deutsche Telekom, CATT, NTT Docomo, InterDigital, Intel Corporation, Huawei |
| R3-212733 | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | Qualcomm Incorporated, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics, Huawei |
| R3-212734 | Supporting use of UE Radio Capability for Paging in RRC_INACTIVE | Qualcomm Incorporated, Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom, LG Electronics, Huawei |
| R3-212735 | CB: # 109_UEradioCapPagingINACTIVE - Summary of email discussion | Qualcomm - moderator |
| R3-212736 | CB: # 110_MICOmode - Summary of email discussion | Nokia - moderator |
| R3-212737 | CB: # 111_UnmappedQoSflowsDisaggregated - Summary of email discussion | CATT - moderator |
| R3-212738 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson, NTT DOCOMO, Deutsche Telekom,Verizon Wireless, |
| R3-212739 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson, NTT DOCOMO, Deutsche Telekom,Verizon Wireless, |
| R3-212740 | Introducing Maximum Integrity Protected Data Rate after EPC to 5GC handover | Huawei, CMCC, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-212741 | CB: # 113_CHOearlyDataFwdMN-eNBchg - Summary of email discussion | Intel - moderator |
| R3-212742 | 36.423 correction for CHO early data forwarding in MN to eNB Change scenario | Intel Corporation, Samsung, LGE |
| R3-212743 | 38.423 correction for CHO early data forwarding in MN to ng-eNB/gNB Change | Intel Corporation, Samsung, LGE |
| R3-212744 | 36.300 correction for CHO early data forwarding in MeNB to eNB Change scenario | Intel Corporation, Samsung, LGE |
| R3-212745 | 37.340 correction for CHO early data forwarding in MN to eNB/gNB Change scenario | Intel Corporation, Samsung, LGE |
| R3-212746 | CB: # 114_AerialAuthInfo - Summary of email discussion | Ericsson - moderator |
| R3-212747 | CB: # 115_InterMNresumeNoMNchg - Summary of email discussion | Qualcimm - moderator |
| R3-212749 | Interactions with other procedures for the UE TNLA BINDING RELEASE | Huawei, China Telecom, Orange |
| R3-212750 | Interactions with other procedures for the UE TNLA BINDING RELEASE | Huawei, China Telecom, Orange |
| R3-212751 | CB: # 116_TNLAbindingRelease - Summary of email discussion | Huawei - moderator |
| R3-212752 | CB: # 117_MaxCGI_E1 - Summary of email discussion | Nokia - moderator |
| R3-212753 | Correction of PDU Session Modify | Nokia, Nokia Shanghai Bell, Orange, ZTE, Ericsson, Huawei |
| R3-212754 | Correction of PDU Type Frame | Nokia, Nokia Shanghai Bell, Orange, Ericsson |
| R3-212755 | CB: # 119_PDUtypeFrame - Summary of email discussion | Nokia - moderator |
| R3-212756 | CB: # 120_PDCPduplicationIssue - Summary of email discussion | Ericsson - moderator |
| R3-212757 | CB: # 121_AbnormalConditionsHOprep - Summary of email discussion | CATT - moderator |
| R3-212758 | CB: # 122_EHCstatusWRT_RAN2 - Summary of email discussion | Huawei - moderator |
| R3-212759 | CR to 37.473 on MeasGapSharingConfig | Huawei, China Unicom |
| R3-212760 | Cause value on S1AP for insufficient UE capabilities CR 36.413 | Ericsson, Deutsche Telekom |
| R3-212761 | Cause value on NGAP for insufficient UE capabilities CR 38.413 | Ericsson, Deutsche Telekom |
| R3-212762 | draft LS to CT4 | Ericsson |
| R3-212763 | CB: # 124_SNinitSNmod - Summary of email discussion | Ericsson - moderator |
| R3-212764 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-212765 | Clarification of the use of the max no of CHO preparations | Nokia, Nokia Shanghai Bell |
| R3-212766 | Clarification on TAI Slice Support List | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-212767 | Clarification on TAI Slice Support List | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-212768 | Clarification on TAI Slice Support List | China Telecom, Nokia, Nokia Shanghai Bell |
| R3-212769 | CB: # 118_PDUsessMod - Summary of email discussion | Nokia - moderator |
| R3-212772 | correction of PDU Type Frame | Nokia, Nokia Shanghai Bell |
| R3-212774 | Correction of PDU Type Frame | Nokia, Nokia Shanghai Bell |
| R3-212775 | Correction of PDU Type Frame | Nokia, Nokia Shanghai Bell, Orange, Ericsson |
| R3-212786 | Addition of sidelink MR-DC resource coordination | Ericsson |
| R3-212787 | Addition of sidelink MR-DC resource coordination | Ericsson, LG Electronics, LGU+, Deutsche Telekom, CATT, NTT Docomo, InterDigital, Intel Corporation, Huawei |
| R3-212796 | Correction on Abnormal Conditions in Handover Preparation Procedure for R15 | CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-212797 | Correction on Abnormal Conditions in Handover Preparation Procedure for R16 | CATT, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-212798 | Correction on BH RLC CH configured for BAP control PDU | Huawei, CATT, Qualcomm , Lenovo, Motorola Mobility,Nokia, Nokia Shanghai Bell |
| R3-212799 | Correction on UL BH information configuration for DRBs support CA based duplication | Huawei, Qualcomm, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell |
| R3-212829 | Correction of en-gNB initiated EN-DC Resource Status Reporting | Huawei, Qualcomm Incorporated, BT, Nokia, Nokia Shanghai Bell, ZTE, Ericssion, NEC |
| R3-212842 | Correction on MLB for TS38.473 [NR_SON_MDT-Core] | ZTE, China Telecom, China Unicom, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT |
| R3-212844 | Correction for UL Data Notification over E1 | Huawei, Intel Corporation, CATT, China Telecom |
| R3-212845 | Correction for UL Data Notification over E1 | Huawei, Intel Corporation, CATT, China Telecom |
| R3-212851 | Correction on SN initiated SN Modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC., ZTE |
| R3-212852 | Correction on SN initiated SN Modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC., ZTE |
| R3-212853 | No partial success in the SN initiated SN Modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC., ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-212854 | No partial success in the SN initiated SN Modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC., ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-212855 | LS on Support of Aerial feature | Ericsson |
| R3-212870 | Maximum Number of RRC connections | Ericsson, CMCC |
| R3-212872 | Maximum number of NRCGI over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung |
| R3-212915 | Correction on NRPPa transaction types | Huawei, CMCC |
| R3-212933 | Maximum number of NRCGI over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung |
| R3-212934 | LS on Insufficient UE Capabilities Cause Value | Ericsson |
| R3-212948 | CB: # 107_Rel-16Corr_IAB - Summary of email discussion | Qualcomm - moderator |
| R3-212957 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson, NTT DOCOMO, Deutsche Telekom,Verizon Wireless, |
| R3-212958 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson, NTT DOCOMO, Deutsche Telekom,Verizon Wireless, |
| R3-212962 | Correction of ASN.1 definition for RESOURCE STATUS REQUEST messageand semantics for Resource Status Reporting Initiation procedure | Samsung, CMCC, ZTE, CATT, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Verizon, Ericssion |
| R3-212964 | Cause value on NGAP for insufficient UE capabilities CR 38.413 | Ericsson, Deutsche Telekom |
| R3-212965 | gNB-DU UE Aggregate Maximum Bit Rate Uplink correction | Ericsson, NTT DOCOMO, Deutsche Telekom,Verizon Wireless, |
| R3-212967 | Maximum number of NRCGI over E1 | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung |
| R3-212979 | Maximum number of NRCGI over E1 [EXT_NRCGI_E1] | Nokia, Nokia Shanghai Bell, Verizon Wireless, Samsung |
| R3-212980 | Correction on SN initiated SN Modification procedure for EN-DC | Ericsson, NTT DOCOMO, INC., ZTE |
| R3-213000 | RACH Report Container(CR to 38423) | China Telecommunication |
| R3-213001 | Correction of ASN.1 definition for RESOURCE STATUS REQUEST messageand semantics for Resource Status Reporting Initiation procedure | Samsung, CMCC, ZTE, CATT, Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, Verizon, Ericssion |
| 9.3.8.2 | Pure Stage-2 Corrections | |
| R3-211672 | DC in same and different DUs | NEC |
| R3-211701 | Serving Cell Information from gNB-DU | ZTE, Nokia, Nokia Shanghai Bell |
| R3-211713 | Support of RAN sharing for the disaggregated SNPN | China Telecommunication |
| R3-211777 | Suspend Configuration | Ericsson, Intel, CATT, Google |
| R3-211778 | Suspend Configuration | Ericsson, Intel, CATT, Google |
| R3-211887 | Correction on NGAP functions | ZTE Corporation |
| R3-211888 | Correction on NGAP functions | ZTE Corporation |
| R3-212044 | RRC Re-establishment and inter-vendor CU operation | Ericsson, Verizon Wireless |
| R3-212045 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless |
| R3-212049 | RRC Re-establishment and inter-vendor CU operation CR 38.401 | Ericsson, Verizon Wireless |
| R3-212220 | Discussion on NRPPa transaction types | Huawei, CMCC |
| R3-212293 | CR for 38.460 on E1AP handling for unmapped DL QoS flows | Intel Corporation, CATT, Huawei |
| R3-212294 | CR for 38.460 on E1AP handling for unmapped DL QoS flows | Intel Corporation, CATT, Huawei |
| R3-212297 | Clean-up on Xn-U Address Indication procedure | Intel Corporation |
| R3-212298 | Clean-up on Xn-U Address Indication procedure | Intel Corporation |
| R3-212451 | Correction on conditional reconfiguration for PSCell | Google Inc., Intel Corporation, CATT |
| R3-212540 | Clarification on the DAPS HO response per E-RABs | Samsung |
| R3-212541 | Clarification on the DAPS HO response per DRBs | Samsung |
| 10.1 | General | |
| R3-211473 | BLCR to 36.423:Support of MDT enhancement | CATT |
| R3-211474 | BLCR to 38.413_Addition of SON features enhancement | Ericsson |
| R3-211475 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| R3-211476 | MDT in MR-DC | Huawei |
| R3-211477 | BLCR to 36.413_Addition of SON features enhancement | Qualcomm |
| R3-211480 | BLCR to 36.300_Addition of SON features enhancement | Lenovo, Motorola Mobility |
| R3-211483 | BLCR to 37.320: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-211491 | MRO for PScell Change Failure | Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-211492 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-211493 | BLCR to 38.401_Addition of SON features enhancement | ZTE |
| R3-211494 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-211495 | BLCR to 38.401: Support of MDT enhancement | CMCC |
| R3-211498 | BLCR to 36.423_Addition of SON features enhancement | CATT |
| R3-211499 | BLCR to 38.463: Support of MDT enhancement | Nokia, Nokia Shanghai Bell |
| R3-211500 | BLCR to 38.473: Support of MDT enhancement | Samsung |
| R3-212469 | Updated work plan for enhancement of data collection for SON_MDT in NR and EN-DC WI | CMCC, Ericsson |
| R3-212657 | CB: # 1201_SONMDT_BLCRs - Summary of email discussion | CMCC - moderator |
| R3-212983 | BLCR to 38.300_Addition of SON features enhancement | CMCC |
| R3-212984 | BLCR to 38.423_Addition of SON features enhancement | Samsung |
| R3-212985 | BLCR to 38.473_Addition of SON features enhancement | Huawei |
| 10.2.1.1 | PCI Selection | |
| R3-212255 | (TP for SON BL CR for TS 38.473) Discussion and solution on PCI Reconfiguration | Ericsson |
| R3-212658 | CB: # 1202_SONMDT_PCISelect - Summary of email discussion | Ericsson - moderator |
| 10.2.1.3 | Successful Handover Report | |
| R3-211856 | Discussion on successful handover report | CATT |
| R3-212130 | Inter-RAT Successful Handover Report | ZTE |
| R3-212131 | (TP for SON BL CR for TS 38.413) Successful Handover support | ZTE |
| R3-212132 | (TP for SON BL CR for TS 38.423) Successful Handover support | ZTE |
| R3-212133 | (TP for SON BL CR for TS 38.473) Successful Handover support | ZTE |
| R3-212250 | Successful Handover Report for CHO and DAPS | Ericsson |
| R3-212268 | Improving RAN visibility over CHO and DAPS procedures via SHR and RLF reports | InterDigital |
| R3-212659 | CB: # 1203_SONMDT_SuccessHO - Summary of email discussion | InterDigital - moderator |
| R3-212935 | LS on UP measurements for Successful Handover Report | Ericsson |
| 10.2.1.4 | UE History Information in EN-DC | |
| R3-211551 | A compromise solution for handling of the SCG UE history information | Nokia, Nokia Shanghai Bell |
| R3-211552 | (TP to TS 38.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG UHI | Nokia, Nokia Shanghai Bell |
| R3-211553 | (TP to TS 36.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG UHI | Nokia, Nokia Shanghai Bell |
| R3-211674 | UE History Information (UHI) in MR-DC | NEC |
| R3-211717 | Discussion on UE history information | China Telecommunication |
| R3-211853 | Enhancement of UE history information in MR-DC scenario | CATT |
| R3-211854 | (TP on UE history information for 36.413) Addition of UE history information for SN | CATT |
| R3-211855 | (TP on UE history information for 36.423) Addition of UE history information for SN | CATT |
| R3-212123 | UE History Information in MR-DC | Qualcomm Incorporated |
| R3-212134 | UE History Information in MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-212135 | (TP for SON BL CR for TS 37.340) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-212136 | (TP for SON BL CR for TS 36.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-212137 | (TP for SON BL CR for TS 38.413) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-212138 | (TP for SON BL CR for TS 38.423) Introduce UHI of MR-DC | ZTE, Lenovo, Motorola Mobility, China Unicom |
| R3-212203 | (TP for SON BLCR for 38.423) UE History Information in MR-DC | Huawei |
| R3-212204 | (TP for SON BLCR for 38.413) UE History Information in MR-DC | Huawei |
| R3-212205 | (TP for SON BLCR for 36.413 and 36.423) UE History Information in EN-DC | Huawei |
| R3-212251 | (TP for SON BL CR for TS 38.423) UE History Information for Secondary Node | Ericsson |
| R3-212470 | UE history information in MR-DC | CMCC |
| R3-212471 | (TP to TS 36.413)UE history information in MR-DC | CMCC |
| R3-212472 | (TP to TS 36.423)UE history information in MR-DC | CMCC |
| R3-212473 | (TP to TS 38.413)UE history information in MR-DC | CMCC |
| R3-212474 | (TP to TS 38.423)UE history information in MR-DC | CMCC |
| R3-212532 | UE History Information in EN-DC | Samsung |
| R3-212533 | TP for SON BLCR for 38.423: UE History Information in EN-DC | Samsung |
| R3-212534 | TP for SON BLCR for 36.423: UE History Information in EN-DC | Samsung |
| R3-212660 | CB: # 1204_SONMDT_UEHistory - Summary of email discussion | CATT - moderator |
| R3-212921 | CB: # 1204_SONMDT_UEHistory - Summary of email discussion | CATT - moderator |
| 10.2.1.5 | Load Balancing Enhancements | |
| R3-211554 | Further discussion on the information on PRB utilisation per slice | Nokia, Nokia Shanghai Bell, ZTE, Deutsche Telekom, BT, China Telecom |
| R3-211555 | (TP to TS 38.473, NR_ENDC_SON_MDT_enh-Core) Adding slice to the load information | Nokia, Nokia Shanghai Bell, ZTE, Deutsche Telekom, BT, China Telecom |
| R3-211569 | (TP for SON BL CR 38.423) Adding slice to the load information | ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom, BT, China Telecom |
| R3-211685 | TP to TS 38.423 on SUL reporting | NEC |
| R3-211686 | TP to TS 38.473 on SUL reporting | NEC |
| R3-211687 | PRB per slice reporting | NEC |
| R3-211861 | (TP on SON for 36.423) Discussion on PSCell MLB and SUL PRB usage | CATT |
| R3-211862 | (TP on SON for 38.423) Support of SUL PRB usage | CATT |
| R3-211863 | (TP on SON for 38.473) Support of SUL PRB usage | CATT |
| R3-212206 | (TP for SON BLCR for 38.423) Load Balancing Enhancements | Huawei |
| R3-212257 | (TP for SON BL CR for TS 38.423) MLB enhancements | Ericsson |
| R3-212258 | (TP for SON BL CR for TS 36.423) MLB enhancements | Ericsson |
| R3-212490 | Additional information to slice PRB usage | CMCC |
| R3-212491 | TP to SON BLCR 38.423 on slice PRB | CMCC |
| R3-212492 | TP to SON BLCR 38.473 on slice PRB | CMCC |
| R3-212661 | CB: # 1205_SONMDT_LoadBalancing - Summary of email discussion | Nokia - moderator |
| R3-212843 | (TP for SON BLCR for 38.423) Load Balancing Enhancements | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom, BT, China Telecom |
| R3-212846 | CB: # 1205_SONMDT_LoadBalancing - Summary of email discussion | Nokia - moderator |
| R3-212849 | (TP to TS 38.473, NR_ENDC_SON_MDT_enh-Core) Adding slice to the load information | Nokia, Nokia Shanghai Bell, ZTE, Deutsche Telekom, BT, China Telecom, Huawei, CMCC, Ericsson |
| R3-212952 | (TP for SON BLCR for 38.423) Load Balancing Enhancements | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Deutsche Telekom, BT, China Telecom, CMCC, Ericsson, CATT |
| 10.2.1.6 | MRO for SN Change Failure | |
| R3-211556 | Solution for MRO for PSCell change failure | Nokia, Nokia Shanghai Bell |
| R3-211557 | (TP to TS 38.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG MRO | Nokia, Nokia Shanghai Bell |
| R3-211558 | (TP to TS 36.423, NR_ENDC_SON_MDT_enh-Core) Enabling SCG MRO | Nokia, Nokia Shanghai Bell |
| R3-211718 | Discussion on MRO for SN Change Failure | China Telecommunication |
| R3-211852 | Consideration on support of SN change failure in case of MR-DC | CATT |
| R3-212124 | MRO for SN Change Failure | Qualcomm Incorporated |
| R3-212139 | Further consideration on MRO SN change failure | ZTE |
| R3-212207 | (TP for SON BLCR for 38.423) MRO for SN Change Failure | Huawei |
| R3-212208 | (TP for SON BLCR for 38.300) MRO for SN Change Failure | Huawei |
| R3-212259 | (TP for SON BL CR for TS 38.423) MRO for SN Change Failure | Ericsson |
| R3-212530 | Support of SN change failure | Samsung |
| R3-212531 | TP for SON BLCR for 38.423: Support of SN change failure | Samsung |
| R3-212662 | CB: # 1206_SONMDT_SNChangeFail - Summary of email discussion | Samsung - moderator |
| R3-212822 | CB: # 1206_SONMDT_SNChangeFail - Summary of email discussion | Samsung - moderator |
| 10.2.1.7 | RACH Optimization Enhancements | |
| R3-211864 | (TP on SON for 38.473) Discussion on Rel-16 leftover issues for PRACH coordination | CATT |
| R3-211865 | (TP on SON for 36.423) TP on PRACH coordination for X2AP | CATT |
| R3-212140 | Left issue for Rel-16 RACH Optimization | ZTE |
| R3-212168 | (TP for SON BL CR for TS 38.473): Left overs on RACH Optimization Enhancements | Huawei |
| R3-212169 | (TP for SON BL CR for TS 38.401):Stage 2 update for RACH Optimization | Huawei |
| R3-212170 | UE RACH report for SN | Huawei |
| R3-212260 | (TP for SON BL CR for TS 38.473) RACH conflict resolution and RACH report availability indication over F1 interface | Ericsson |
| R3-212376 | RACH Optimization Further Discussion | Nokia, Nokia Shanghai Bell |
| R3-212377 | (TP for SON BL CR to TS 38.423) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-212378 | (TP for SON BL CR to TS 38.473) Enhancement of RACH Conflict Resolution | Nokia, Nokia Shanghai Bell |
| R3-212663 | CB: # 1207_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| R3-212819 | CB: # 1207_SONMDT_RACH - Summary of email discussion | Nokia - moderator |
| 10.2.2 | Coverage and Capacity Optimization | |
| R3-211690 | Remaining Open point on CCO over F1 | NEC |
| R3-211691 | (TP for SON BL CR 38.300) Coverage and Capacity Optimization | NEC |
| R3-212125 | Coverage and Capacity Optimization | Qualcomm Incorporated |
| R3-212209 | (TP for SON BLCR for 38.473) Coverage and Capacity Optimization | Huawei |
| R3-212261 | (TP for SON BL CR for TS 38.423) CCO | Ericsson |
| R3-212262 | (TP for SON BL CR for TS 38.300) CCO | Ericsson |
| R3-212263 | (TP for SON BL CR for TS 38.473) CCO | Ericsson |
| R3-212327 | Further analysis on beam aspects and split architecture for CCO | Nokia, Nokia Shanghai Bell |
| R3-212529 | TP for SON BLCR for 38.300: Support of CCO | Samsung |
| R3-212582 | Further Discussion on Coverage and Capacity Optimization in NR | ZTE, China Telecom, China Unicom |
| R3-212583 | (TP for SON BL CR 38.300) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-212584 | (TP for SON BL CR 38.423) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-212585 | (TP for SON BL CR 38.473) Coverage and Capacity Optimization | ZTE, China Telecom, China Unicom |
| R3-212664 | CB: # 1208_SONMDT_CCO - Summary of email discussion | Huawei - moderator |
| R3-212816 | CB: # 1208_SONMDT_CCO - Summary of email discussion | Huawei - moderator |
| 10.2.3 | Inter-System Inter-RAT Energy Saving | |
| R3-212011 | (TP for SON BL CR for TS 38.300): Minimum activation time for energy saving) | Huawei |
| R3-212141 | Discussion on Minimum Activation Time | ZTE |
| R3-212142 | (TP for SON BL CR for TS 36.300) RAN energy efficiency | ZTE |
| R3-212143 | (TP for SON BL CR for TS 38.300) RAN energy efficiency | ZTE |
| R3-212144 | (TP for SON BL CR for TS 38.413) RAN energy efficiency | ZTE |
| R3-212328 | (TP for BLCR to TS 38.300): Description of minimum activation time | Nokia, Nokia Shanghai Bell |
| R3-212468 | Discussion on inter-system inter-RAT energy saving | CMCC |
| R3-212475 | TP to 38.413 for inter-system inter-RAT energy saving | CMCC |
| R3-212665 | CB: # 1209_SONMDT_InterSystemEnergy - Summary of email discussion | CMCC - moderator |
| R3-212805 | (TP for BL CR to TS 38.300) Inter-system Inter-RAT Energy Saving | CMCC |
| R3-212817 | (TP for BL CR to TS 38.300) Inter-system Inter-RAT Energy Saving | CMCC |
| 10.2.4 | Inter-System Load Balancing | |
| R3-212126 | Inter-System Load Balancing | Qualcomm Incorporated |
| R3-212210 | (TP for SON BLCR for 38.413) Inter-System Load Balancing | Huawei |
| R3-212211 | (TP for SON BLCR for 38.413) Reporting NR capable UEs | Huawei |
| R3-212256 | (TP for SON for TS 38.413, TS 38.300, TS 36.300) Inter-System Load Balancing BL CR | Ericsson |
| R3-212493 | Load metrics for inter-system load balancing | CMCC |
| R3-212494 | TP to 36.300 for inter-system load balancing | CMCC |
| R3-212495 | TP to 38.300 for inter-system load balancing | CMCC |
| R3-212587 | Further Discussion on Inter-system Load Balancing in NR | ZTE, China Telecom, China Unicom |
| R3-212588 | (TP for SON BL CR 38.413) Inter-system Load Balancing | ZTE, CMCC, China Telecom, China Unicom |
| R3-212666 | CB: # 1210_SONMDT_InterSystemLoad - Summary of email discussion | ZTE - moderator |
| 10.2.5 | Two-Step RACH Optimization | |
| R3-211437 | Reply LS on RACH report for 2-step RACH | RAN2 |
| R3-212252 | 2-step RACH optimization for SON | Ericsson |
| R3-212375 | Scrambling Sequence Generation Coordination Between gNB | Nokia, Nokia Shanghai Bell |
| R3-212667 | CB: # 1211_SONMDT_2StepRACH - Summary of email discussion | Ericsson - moderator |
| 10.2.6 | Mobility Enhancement Optimization | |
| R3-211422 | LS on UE context keeping in the source cell | RAN2 |
| R3-211561 | CHO information in the UE context | Nokia, Nokia Shanghai Bell |
| R3-211562 | Response LS on UE context keeping in the source cell | Nokia, Nokia Shanghai Bell |
| R3-211848 | Discussion on MRO for CHO mobility enhance | CATT |
| R3-211849 | [Draft]LS on MRO for CHO mobility Enhancement | CATT |
| R3-211850 | Discussion on MRO for DAPS mobility enhance | CATT |
| R3-211851 | [Draft]LS on MRO for DAPS mobility Enhancement | CATT |
| R3-211959 | TP for TS38.300: SON enhancements for CHO | Samsung |
| R3-211960 | TP for SON BLCR for 38.423: Support of CHO for MRO | Samsung |
| R3-211961 | Reply LS on UE context keeping in the source cell | Samsung |
| R3-212128 | Logged MDT Enhancements | Qualcomm Incorporated |
| R3-212145 | Scenarios of Mobility Enhancement Optimization | ZTE |
| R3-212158 | SON Enhancements for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-212159 | (TP for SON BLCR for 38.300): MRO for CHO | Lenovo, Motorola Mobility, ZTE |
| R3-212160 | SON Enhancements for DAPS Handover | Lenovo, Motorola Mobility, ZTE |
| R3-212161 | (TP for SON BLCR for 38.300): MRO for DAPS handover | Lenovo, Motorola Mobility, ZTE |
| R3-212162 | [Draft] Reply LS on UE context keeping in the source cell | Lenovo, Motorola Mobility |
| R3-212163 | Update of Way forward on Scenarios for SON enhancements for CHO and DAPS HO | Lenovo, Motorola Mobility |
| R3-212201 | Keeping UE context in the source cell | Huawei, Qualcomm |
| R3-212202 | [draft] Reply LS on UE context keeping in the source cell | Huawei, Qualcomm |
| R3-212212 | (TP for SON BLCR for 38.300) Mobility Enhancement Optimization | Huawei |
| R3-212253 | (TP for SON BL CR for TS 38.300) DAPS handover SON aspects | Ericsson |
| R3-212254 | (TP for SON BL CR for TS 38.300) Mobility Robustness Optimization for Conditional Handover | Ericsson |
| R3-212361 | UE context keeping in the source cell | Ericsson |
| R3-212362 | [DRAFT] Reply LS on UE context keeping in the source cell | Ericsson |
| R3-212398 | Discussion on use cases for MRO of DAPS HO | LG Electronics |
| R3-212404 | Discussion on SON enhancements for CHO | Samsung |
| R3-212590 | Discussion on MRO for DAPS | Samsung |
| R3-212668 | CB: # 1212_SONMDT_MobEnh - Summary of email discussion | Lenovo - moderato |
| R3-212891 | [DRAFT] Reply LS on UE context keeping in the source cell | Ericsson |
| R3-212944 | Reply LS on UE context keeping in the source cell | Ericsson |
| R3-212960 | Update of Way forward on Scenarios for SON enhancements for CHO and DAPS HO | Lenovo, Motorola Mobility |
| 10.3.2.1 | MDT Enhancements | |
| R3-211463 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover | SA3 |
| R3-211976 | Propagation for Management Based MDT PLMN List | Samsung |
| R3-211977 | Propagation for Management Based MDT PLMN List | Samsung |
| R3-212002 | Discussion on propagation of user consent related information during Xn inter-PLMN handover | Huawei |
| R3-212003 | Propagation of user consent related information during Xn inter-PLMN handover | Huawei |
| R3-212012 | Miscellaneous corrections to MDT (Multiple TPs included) | Huawei |
| R3-212120 | (TP for MDT BL CR for TS38.423) TP on updates related to the Management based MDT PLMN list processing based on the SA3 LS | Ericsson |
| R3-212121 | (draft) Reply LS on Management Based MDT PLMN List | Ericsson |
| R3-212264 | (TP for MDT BL CR for TS 38.413, TS 38.423, TS 38.373, TS 38.463) Introduction of the Report Amount | Ericsson |
| R3-212265 | [DRAFT] LS on the introduction of the Report amount configuration for the MDT measurements | Ericsson |
| R3-212669 | CB: # 1213_SONMDT_MDTEnh - Summary of email discussion | Huawei - moderator |
| R3-212823 | (TP for MDT BL CR for TS 37.320): PLMN checking during UE context retrieval | Huawei |
| R3-212824 | LS on Area scope configuration and Frequency band info in MDT configuration | Huawei |
| R3-212828 | CB: # 1213_SONMDT_MDTEnh - Summary of email discussion | Huawei - moderator |
| R3-212939 | [DRAFT] LS on Report Amount for M5, M5, M6, M7 measurements | Ericsson |
| R3-212961 | LS on Report Amount for M5, M5, M6, M7 measurements | Ericsson |
| 10.3.2.2 | MDT for MR-DC | |
| R3-212013 | MDT for MR-DC (Multiple TPs included) | Huawei |
| R3-212127 | Mobility Enhancement Optimization | Qualcomm Incorporated |
| R3-212571 | MDT for MR-DC | ZTE |
| R3-212572 | (TP for 38.423) MDT for MR-DC | ZTE |
| R3-212670 | CB: # 1214_SONMDT_MDT-MR-DC - Summary of email discussion | Qualcomm - moderator |
| R3-212876 | CB: # 1214_SONMDT_MDT-MR-DC - Summary of email discussion | Qualcomm - moderator |
| 10.4 | Support for L2 Measurements | |
| R3-212266 | On L2 (M6) Measurements | Ericsson |
| R3-212573 | Support for L2 Measurements | ZTE |
| R3-212671 | CB: # 1215_SONMDT_L2 - Summary of email discussion | Ericsson - moderator |
| R3-212929 | CB: # 1215_SONMDT_L2 - Summary of email discussion | Ericsson - moderator |
| 10.5 | SON/MDT Optimizations for NR-U | |
| R3-211731 | Load information enhancements for NR-U | Nokia, Nokia Shanghai Bell |
| R3-212167 | SON enhancements for NR-U | Lenovo, Motorola Mobility |
| R3-212267 | Proposals on MLB for NR-U | Ericsson |
| R3-212581 | Optimization for NR-U | ZTE |
| R3-212672 | CB: # 1216_SONMDT_NR-U - Summary of email discussion | Nokia - moderator |
| 12.1 | General | |
| R3-211916 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei, Ericsson |
| R3-212673 | CB: # 1101_IOT_Gen - Summary of email discussion | Ericsson - moderator |
| 12.2 | Support for Carrier Selection and Carrier Specific Configuration | |
| R3-211588 | Discussion on Carrier Selection and Carrier Specific Configuration | ZTE |
| R3-211589 | 36.413 (Rel-17) Introduction of CEL based paging carrier selection for Option 1 | ZTE |
| R3-211590 | 36.413 (Rel-17) Introduction of paging carrier information for Option 2 | ZTE |
| R3-211649 | Support of Carrier Selection based on coverage level | Nokia, Nokia Shanghai Bell |
| R3-211650 | Support of Carrier Selection based on coverage level | Nokia, Nokia Shanghai Bell |
| R3-211917 | Consideration on NB-IoT Carrier Selection | Huawei |
| R3-211918 | Support of Additional enhancements for NB-IoT and LTE-MTC | Huawei |
| R3-211919 | Consideration on Rel-17 enhancements for NB-IoT and LTE-MTC | Huawei |
| R3-212355 | Discussion on NB-IoT paging carrier selection | Ericsson |
| R3-212674 | CB: # 1102_IOT_Main - Summary of email discussion | Huawei - moderator |
| R3-212715 | Response paper to R3-211588, R3-211590, R3-211650, R3-211918 | Ericsson Telecomunicazioni SpA |
| 13.1 | General | |
| R3-211489 | BL CR to XnAP on Rel-17 eIAB | Samsung, Nokia, Nokia Shanghai Bell, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-211490 | CR on CP-UP separation for Rel-17 IAB | Nokia, Nokia Shanghai Bell, Samsung, Verizon, Qualcomm Incorporated, CATT, ZTE, Fujitsu, AT&T, KDDI, Lenovo, Motorola Mobility, LG Electronics |
| R3-211501 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-211738 | Updated Workplan for Rel-17 IAB | Qualcomm Incorporated (WI Rapporteur) |
| R3-212675 | CB: # 36_IAB_general - Summary of email discussion | Qualcomm - moderator |
| R3-212723 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-212837 | CP-based Congestion Indication for IAB Networks | Ericsson |
| R3-212989 | CP-based Congestion Indication for IAB Networks | Ericsson |
| 13.2.1.1 | Procedure Details | |
| R3-211724 | IAB Inter-donor Topology Adaptation | Ericsson |
| R3-211739 | Inter-donor Topology Adaptation Procedures | Qualcomm Incorporated |
| R3-211891 | discussion on Inter-Donor IAB Node Migration | Nokia, Nokia Shanghai Bell |
| R3-211939 | Discussion on terminating point for inter-donor IAB node migration procedure | Samsung, Qualcomm, Fujitsu, Google, ZTE, AT&T, Verizon |
| R3-211940 | Discussion on inter-donor IAB node migration procedure for Rel-17 eIAB | Samsung |
| R3-212037 | Further considerations on inter-donor migration | ZTE |
| R3-212046 | Discussion on inter-donor IAB migration | Fujitsu |
| R3-212122 | Considerations on inter-donor IAB migration | KDDI Corporation |
| R3-212164 | Remaining issues for IAB inter-donor migration | Lenovo, Motorola Mobility |
| R3-212249 | Implications of inter-donor IAB migration | InterDigital |
| R3-212413 | IAB topology update procedure | Huawei |
| R3-212653 | Response to R3-211939 on the terminating point for inter-donor IAB node migration procedure | Qualcomm, Samsung, Google, Fujitsu |
| R3-212676 | CB: # 37_IAB_InterDonorMigrationDetails - Summary of email discussion | Samsung - moderator |
| R3-212725 | Discussion on terminating point for inter-donor IAB node migration procedure | Samsung, Qualcomm, Fujitsu, Google, ZTE, AT&T, Verizon, CATT |
| R3-212858 | CB: # 37_IAB_InterDonorMigrationDetails - Summary of email discussion | Samsung - moderator |
| R3-212880 | LS on Inter-donor migration | Samsung |
| R3-212886 | CR on inter-donor IAB migration | Huawei |
| R3-212971 | CR on inter-donor IAB migration | Huawei |
| R3-212972 | LS on Inter-donor migration | Samsung |
| R3-212981 | LS on Inter-donor migration | Samsung |
| 13.2.1.2 | CHO and DAPS | |
| R3-211424 | Reply LS on DAPS-like solution for service interruption reduction | RAN2 |
| R3-211725 | On the Use of Conditional Handover and Dual IAB Protocol Stack in IAB Networks | Ericsson |
| R3-211799 | IAB topology adaptation (CHO&DAPS-like and Procedure Details) | CATT |
| R3-212083 | Considerations on intra-CU CHO | KDDI Corporation |
| R3-212677 | CB: # 37bis_IAB_CHO-DAPS - Summary of email discussion | Ericsson - moderator |
| 13.2.2 | Reduction of Service Interruption | |
| R3-211726 | Reduction of Service interruption in IAB-node Migration | Ericsson |
| R3-211740 | Interruption time reduction for Intra-donor IAB-node Migration | Qualcomm Incorporated |
| R3-211800 | Reduction the Service Interruption | CATT |
| R3-211892 | Discussion on Reduction of Service Interruption during Intra-Donor Topology Adaptation | Nokia, Nokia Shanghai Bell |
| R3-211941 | Discussion on Service Interruption Reduction and packet loss for Rel-17 IAB | Samsung |
| R3-212038 | Discussion on reduction of service interruption, intra-donor CHO and RLF | ZTE |
| R3-212047 | Transferring RRC Reconfiguration for descendant IAB over source path | Fujitsu |
| R3-212390 | Options to transfer RRCReconfiguration for descendent IAB node over source path | AT&T |
| R3-212414 | Reduction of Service Interruption for IAB topology update | Huawei |
| R3-212678 | CB: # 38_IAB_SvcIntRed - Summary of email discussion2931 | AT&T - moderator |
| R3-212946 | LS to RAN2 on reduction of service interruption during intra-donor IAB-node migration | AT&T |
| R3-212973 | LS to RAN2 on reduction of service interruption during intra-donor IAB-node migration | AT&T |
| 13.2.3 | Topology Redundancy | |
| R3-211412 | Reply LS on inter-donor topology redundancy | RAN WG1 |
| R3-211741 | Backhaul transport for inter-donor redundancy | Qualcomm Incorporated |
| R3-211801 | CP-UP separation and inter-donor topology redundancy | CATT |
| R3-211893 | discussion on Inter-CU topology redundancy | Nokia, Nokia Shanghai Bell |
| R3-211942 | Discussion on topology redundancy for Rel-17 IAB | Samsung |
| R3-212039 | Discussion on CP/UP separation and topology redundancy | ZTE |
| R3-212048 | Discussion on the inter-donor topology redundancy | Fujitsu |
| R3-212165 | Discussion on IAB inter-donor topology redundancy | Lenovo, Motorola Mobility |
| R3-212384 | Open issues on topological redundancy for IAB | LG Electronics |
| R3-212415 | Inter-CU topology redundancy | Huawei |
| R3-212679 | CB: # 39_IAB_TopoRed - Summary of email discussion | Qualcomm - moderator |
| 13.3.1 | Congestion Mitigation | |
| R3-211727 | Congestion Mitigation in IAB Networks | Ericsson |
| R3-211802 | Congestion Mitigation for CP-based and UP-based | CATT |
| R3-211889 | (TP for IAB BLCR 38.473) IAB Congestion Mitigation MPS exemption | Perspecta Labs, CISA ECD |
| R3-211894 | Analysis on Congestion mitigation | Nokia, Nokia Shanghai Bell |
| R3-211943 | Discussion on CP-based and UP-based congestion mitigation in Rel-17 IAB | Samsung |
| R3-212040 | Discussion on congestion control in R17-IAB | ZTE |
| R3-212166 | Discussion on congestion mitigation for IAB | Lenovo, Motorola Mobility |
| R3-212393 | Issues on CP-based congestion indication | LG Electronics |
| R3-212416 | (TP for NR_IAB_enh BL CR for TS 38.473): IAB E2E congestion mitigation | Huawei |
| R3-212680 | CB: # 40_IAB_CongestionMitigation - Summary of email discussion | ZTE - moderator |
| R3-212888 | CP-based Congestion Mitigation for IAB Network | ZTE |
| R3-212923 | CB: # 40_IAB_CongestionMitigation - Summary of email discussion | ZTE - moderator |
| R3-212931 | CB: # 40_IAB_CongestionMitigation - Summary of email discussion | ZTE - moderator |
| R3-212947 | (TP to NR_IAB BL CR to TS 38.473) CP-based Congestion Mitigation for IAB | ZTE |
| 13.3.2 | Multi-Hop Performance: QoS, Latency, Fairness | |
| R3-211728 | On QoS, Latency, and Fairness in IAB Networks | Ericsson |
| R3-211803 | Inter-donor-DU re-routing | CATT |
| R3-211895 | discussion on Inter-Donor-DU re-routing | Nokia, Nokia Shanghai Bell |
| R3-211944 | Discussion on inter-donor-DU re-routing | Samsung |
| R3-212041 | Discussion on multi-hop latency and inter-donor-DU local re-routing | ZTE |
| R3-212417 | Inter-donor-DU re-routing for IAB | Huawei |
| R3-212681 | CB: # 41_IAB_MultiHopPerf - Summary of email discussion | Nokia - moderator |
| 13.4.1 | Resource Multiplexing of Child and Parent Links and CLI Management | |
| R3-211729 | Resource Coordination in IAB Networks | Ericsson |
| R3-211742 | Inter-donor coordination for gNB cell resource multiplexing | Qualcomm Incorporated |
| R3-211945 | Discussion on Resource multiplexing in Rel-17 IAB | Samsung |
| R3-212042 | Discussion on inter-donor coordination in multi-parent scenarios | ZTE |
| R3-212418 | Resource coordination for inter-donor routing | Huawei |
| R3-212682 | CB: # 42_IAB_ResMPX - Summary of email discussion | Huawei - moderator |
| R3-212869 | CB: # 42_IAB_ResMPX - Summary of email discussion | Huawei - moderator |
| R3-212887 | Draft LS on IAB resource multiplexing | Huawei |
| R3-212974 | LS on IAB resource multiplexing | Huawei |
| 14.1 | General | |
| R3-211581 | SCG BL CR to TS 37.340 | ZTE |
| R3-211582 | CPAC BL CR to TS38.401 | ZTE |
| R3-211908 | (SCG BL CR)Support of SCG activation and deactivation | Huawei |
| R3-211909 | (SCG BL CR)Support of CPAC | Huawei |
| R3-212643 | CB: # MRDC1-BL_CR - Summary of email discussion | ZTE - moderator |
| R3-212770 | SCG BL CR to TS 37.340 | ZTE |
| R3-212771 | CPAC BL CR to TS38.401 | ZTE |
| R3-212777 | SCG BL CR to TS 37.340 | ZTE |
| R3-212778 | CPAC BL CR to TS38.401 | ZTE |
| R3-212987 | SCG BL CR to TS 37.340 | ZTE |
| R3-212988 | (SCG BL CR)Support of SCG activation and deactivation | Huawei |
| R3-212991 | SCG BL CR to TS 36.423 | Nokia |
| R3-212992 | SCG BL CR to TS 38.423 | Ericsson |
| R3-212993 | SCG BL CR to TS 38.473 | Samsung |
| R3-212994 | CPAC BL CR to TS 36.423 | Nokia, Nokia Shanghai Bell |
| R3-212995 | CPAC BL CR to TS 37.340 | Huawei |
| R3-212996 | CPAC BL CR to TS 38.420 | China Telecom |
| R3-212997 | CPAC BL CR to TS 38.423 | Ericsson |
| R3-212998 | CPAC BL CR to TS 36.420 | China Telecom |
| 14.2 | Signaling Support for Efficient Activation/Deactivation for One SCG and SCells | |
| R3-211563 | Principles for activation and deactivation of SCG resources | Nokia, Nokia Shanghai Bell |
| R3-211564 | (TP to TS 38.423, LTE_NR_DC_enh2-Core) Adding first procedures for the fast SCG activation/deactivation | Nokia, Nokia Shanghai Bell |
| R3-211565 | (TP to TS 36.423, LTE_NR_DC_enh2-Core) Adding first procedures for the fast SCG activation/deactivation | Nokia, Nokia Shanghai Bell |
| R3-211600 | TP for SCG BL draftCR to TS37.340 | ZTE |
| R3-211601 | TP for SCG BL CR to TS38.423 and TS36.423 | ZTE |
| R3-211602 | TP for SCG BL CR to TS38.473 and TS38.463 | ZTE |
| R3-211675 | SCG Activation / deactivation discussion on X2/Xn | NEC |
| R3-211676 | SCG Activation / deactivation discussion on E1 | NEC |
| R3-211677 | SCG Activation / deactivation discussion on F1 | NEC |
| R3-211759 | SCG activation/deactivation procedure | Qualcomm Incorporated |
| R3-211784 | Efficient SCG (de)activation | Ericsson |
| R3-211785 | Introduction of SCG (de)activatio over X2 | Ericsson |
| R3-211786 | Introduction of SCG (de)activation over Xn | Ericsson |
| R3-211830 | Discussion on efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-211831 | CR to TS 38.423 for efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-211832 | CR to TS 38.473 for efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-211910 | (TP to SCG TS 38.423/38.473 BL CRs) Remaining open issues on SCG activation and deactivation | Huawei |
| R3-211911 | (TP to SCG TS 38.463 BL CR) SCG activation and deactivation in E1 | Huawei, InterDigital |
| R3-211912 | (TP to SCG TS 38.401 BL CR) SCG activation and deactivation in disaggregated NG-RAN architecture | Huawei, InterDigital |
| R3-211963 | CR to TS 38.423 for efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-211964 | CR to TS 38.473 for efficient Activation/Deactivation Mechanism for SCG | CATT |
| R3-212174 | Discussion on SCG (de)activation rejection | Lenovo, Motorola Mobility |
| R3-212175 | Miscellaneous issues on SCG activation and deactivation | Lenovo, Motorola Mobility |
| R3-212176 | Support of SCG Activation and Deactivation | Lenovo, Motorola Mobility |
| R3-212248 | SCG deactivation and re-activation | InterDigital |
| R3-212391 | Open issues on Activation/Deactivation for One SCG and SCells | LG Electronics |
| R3-212537 | Discussion on SCG activation and deactivation | Samsung |
| R3-212538 | BL CR to TS38.473 on SCG (de-)activation | Samsung |
| R3-212644 | CB: # MRDC2-SCG_activation_deactivation - Summary of email discussion | Lenovo - moderato |
| R3-212726 | TP for SCG BL CR to TS38.423 and TS36.423 | ZTE |
| R3-212784 | CB: # MRDC2-SCG_activation_deactivation - Summary of email discussion | Lenovo - moderato |
| R3-212803 | TP for SCG BL draftCR to TS37.340 | ZTE |
| R3-212832 | (TP to SCG TS 38.401 BL CR) SCG activation and deactivation in disaggregated NG-RAN architecture | Huawei, InterDigital |
| R3-212899 | (TP for TS 38.473 on eMRDC) Adding first procedures for the fast SCG activation/deactivation | Samsung |
| R3-212909 | (TP for SCG BL CR for TS 38.423) New indicator in the request messages | Ericsson |
| R3-212924 | (TP to TS 36.423, LTE_NR_DC_enh2-Core) Adding first procedures for the fast SCG activation/deactivation | Nokia, Nokia Shanghai Bell |
| 14.3 | Signaling Support for Conditional PSCell Change/Addition | |
| R3-211423 | LS on Conditional PSCell Addition/Change agreements | RAN2 |
| R3-211566 | Further details of the inter-SN CPC | Nokia, Nokia Shanghai Bell |
| R3-211567 | (TP to TS 38.423, LTE_NR_DC_enh2-Core) Adding first procedures for the CPAC | Nokia, Nokia Shanghai Bell |
| R3-211568 | (TP to TS 36.423, LTE_NR_DC_enh2-Core) Adding first procedures for the CPAC | Nokia, Nokia Shanghai Bell |
| R3-211583 | TP for CPAC BL CR to TS 37.340 | ZTE |
| R3-211584 | TP for CPAC BL CR to TS38.401 | ZTE |
| R3-211585 | TP for CPAC BL CR to TS 38.423 | ZTE |
| R3-211678 | discussion on Conditional PSCell Addition and PSCell Change | NEC |
| R3-211679 | Introducing CPAC to 36.423 | NEC |
| R3-211680 | Introducing CPAC to 38.423 | NEC |
| R3-211714 | Discussion on Conditional PScell Addition/Change procedures | China Telecommunication |
| R3-211715 | TP on 36.423 for introducing CPAC information in SgNB Addition procedure | China Telecommunication |
| R3-211716 | TP on 38.423 for introducing CPAC information in SN Addition procedure | China Telecommunication |
| R3-211756 | SN initiated Inter-SN CPC procedure: preparation, execution, and data forwarding | Qualcomm Incorporated |
| R3-211757 | CPA and MN initiated Inter-SN CPC procedures: preparation, execution, and data forwarding | Qualcomm Incorporated |
| R3-211758 | CPAC replace procedure | Qualcomm Incorporated |
| R3-211833 | Further Considerations on Conditional PSCell Change/Addition | CATT |
| R3-211834 | CR to TS 38.473 for Conditional PSCell Change/Addition | CATT |
| R3-211913 | (TP to CPAC TS 37.340 BL CR) Consideration on conditional PSCell change/addition | Huawei |
| R3-211914 | (TP to CPAC TS 38.401 BL CR) CPAC in disaggregated NG-RAN architecture | Huawei |
| R3-211915 | (TP to CPAC TS 38.420, 36.420 BL CRs) New procedure to support CPAC between RAN nodes | Huawei |
| R3-211965 | CR to TS 38.473 for Conditional PSCell Change/Addition | CATT |
| R3-212177 | Discussion on CPAC | Lenovo, Motorola Mobility |
| R3-212358 | Support of conditional PSCell change/addition | Ericsson |
| R3-212359 | Conditional SN Addition | Ericsson |
| R3-212370 | Conditional SN Addition | Ericsson |
| R3-212392 | Open issues on conditional PScell Change/Addition | LG Electronics |
| R3-212444 | Execution of CPA and inter-SN CPC | Google Inc. |
| R3-212447 | Execution of CPA and inter-SN CPC | Google Inc. |
| R3-212542 | Correction on the preparation of multiple PSCells in one CPAC procedure_38.423 | Samsung |
| R3-212543 | Correction on the preparation of multiple PSCells in one CPAC procedure_36.423 | Samsung |
| R3-212544 | Discussion on the baseline of the CPAC procedure | Samsung |
| R3-212645 | CB: # MRDC3-PSCell_Change_Addition - Summary of email discussion | Huawei - moderator |
| R3-212781 | Execution of CPA and inter-SN CPC | Google Inc. |
| R3-212782 | Execution of CPA and inter-SN CPC | Google Inc. |
| R3-212785 | CB: # MRDC3-PSCell_Change_Addition - Summary of email discussion | Huawei - moderator |
| R3-212833 | (TP to CPAC TS 37.340 BL CR) Consideration on conditional PSCell change/addition | Huawei |
| R3-212834 | (TP to CPAC 36.420 BL CR) New X2AP procedure to support CPAC | Huawei |
| R3-212861 | (TP to TS 38.423, LTE_NR_DC_enh2-Core) Adding CPAC Procedure | Samsung |
| R3-212862 | (TP to TS 36.423, LTE_NR_DC_enh2-Core) Adding CPAC Procedure | Samsung |
| R3-212968 | (TP to TS 38.423, LTE_NR_DC_enh2-Core) Adding CPAC Procedure | Samsung |
| R3-212969 | (TP to TS 36.423, LTE_NR_DC_enh2-Core) Adding CPAC Procedure | Samsung |
| 15.1 | General | |
| R3-212394 | Workplan for Rel-17 NR QoE in RAN3 | China Unicom |
| R3-212637 | CB: # NRQoE1-work_plan - Summary of email discussion | China Unicom - moderator |
| 15.2.1.1 | Configuration, Activation and Deactivation Procedures | |
| R3-211835 | Discussion on NR QoE configuration procedures | CATT |
| R3-211985 | Procedures for Configuration, Activation and Deactivation of QMC | Ericsson |
| R3-212322 | Baseline and stage 2 aspects for NR QoE | Nokia, Nokia Shanghai Bell |
| R3-212323 | Introduction of QoE Measurement Collection for NR | Nokia, Nokia Shanghai Bell |
| R3-212434 | Consideration on NR QoE activation procedure | ZTE Corporation, China Telecom, China Unicom |
| R3-212519 | Further analysis on spec impacts on configuration and reporting | Huawei |
| R3-212520 | CR to 38.413 on Introduction of QoE measurement | Huawei |
| R3-212638 | CB: # NRQoE2-Activation_Deactivation - Summary of email discussion | ZTE - moderator |
| R3-212815 | CR to 38.413 on Introduction of QoE measurement | Huawei |
| R3-212906 | LS on how to support the (de)activation and failure handling of NR QMC | ZTE |
| R3-212956 | LS on how to support the (de)activation and failure handling of NR QMC | ZTE |
| R3-212970 | LS on (de)activation and failure handling of NR QMC | ZTE |
| R3-212975 | LS on (de)activation and failure handling of NR QMC | ZTE |
| 15.2.1.2 | Configuration Details | |
| R3-211732 | NR QoE configuration and reporting | Qualcomm Incorporated |
| R3-211733 | (TP for 38.413 and 38.423) NR QoE configuration and reporting | Qualcomm Incorporated |
| R3-211734 | Per slice QoE measurements | Qualcomm Incorporated |
| R3-211836 | Discussion on NR QoE configuration details | CATT |
| R3-211837 | Discussion on per-slice QoE measurement | CATT |
| R3-211978 | RAN3 impacts for supporting QoE Measurement Collection in NR | Samsung |
| R3-211979 | Support of NR QoE Measurement Collection | Samsung |
| R3-211980 | Support of NR QoE Measurement Collection | Samsung |
| R3-211986 | QoE Configuration and Reporting | Ericsson |
| R3-211987 | paper 3 | Ericsson |
| R3-212324 | Principles for configuration of NR QoE measurements | Nokia, Nokia Shanghai Bell |
| R3-212380 | paper 33 | Ericsson |
| R3-212381 | CR TS 38.413 QoE Configuration and Reporting - Signalling Design | Ericsson |
| R3-212435 | Discussion on NR QoE Configuration | ZTE Corporation, China Telecom |
| R3-212440 | (TP for TS 38.300) Introduce NR QoE | ZTE Corporation, China Telecom |
| R3-212441 | Discussion on configuration details in NR standalone mode | LG Electronics |
| R3-212442 | (TP for TS 38.413) NR QOE configuration | ZTE Corporation, China Telecom |
| R3-212443 | (TP for TS 38.423) NR QOE configuration | ZTE Corporation, China Telecom |
| R3-212498 | Per-slice QoE measurement | CMCC |
| R3-212518 | Further analysis on spec impacts of the potential solutions to QoE measurement per slice | Huawei |
| R3-212521 | Further analysis on spec impacts on RAN intervention of QoE measurement | Huawei |
| R3-212591 | On per-slice QoE measurement | Nokia, Nokia Shanghai Bell |
| R3-212639 | CB: # NRQoE3-RANConfig - Summary of email discussion | Huawei - moderator |
| R3-212838 | CR TS 38.413 QoE Configuration and Reporting - Signalling Design | Ericsson |
| R3-212873 | LS on the mapping between service types and slice at application | Qualcomm |
| R3-212904 | LS on the mapping between service types and slice at application | Qualcomm |
| 15.2.2 | Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | |
| R3-211735 | QoE measurement collection and reporting continuity in mobility scenarios | Qualcomm Incorporated |
| R3-211838 | Discussion on Measurement Collection and Continuity in Mobility | CATT |
| R3-211988 | QoE Mobility Support | Ericsson |
| R3-212445 | Measurement Collection and Continuity in Intra-System Intra-RAT Mobility | ZTE Corporation, China Telecom, China Unicom |
| R3-212640 | CB: # NRQoE4-Mobility - Summary of email discussion | Qualcomm - moderator |
| R3-212874 | LS on the area handling for QoE during mobility | Qualcomm |
| R3-212875 | LS on the QoE requirement for ongoing session continuity | Qualcomm |
| R3-212953 | LS on requirement for configuration changes of ongoing QMC sessions | Qualcomm |
| R3-212976 | LS on the area handling for QoE during mobility | Qualcomm |
| 15.3 | Support for RAN-Visible QoE | |
| R3-211736 | RAN visible QoE | Qualcomm Incorporated |
| R3-211839 | Discussion on relevant set of RAN-visible QoE parameters | CATT |
| R3-211840 | Discussion on RAN visible QoE configuration and reporting | CATT |
| R3-211981 | Discussion on RAN visible QoE | Samsung |
| R3-211989 | RAN-visible QoE Services and Metrics | Ericsson |
| R3-211990 | RAN-visible QoE - Configuration and Reporting | Ericsson |
| R3-212325 | Analysis of QoE metrics for use by the NG-RAN | Nokia, Nokia Shanghai Bell |
| R3-212448 | Further consideration on RAN visible QoE | ZTE Corporation, China Telecom |
| R3-212497 | RAN visible QoE metrics | CMCC |
| R3-212515 | Further analysis on spec impacts of the potential solutions to QoE visibility | Huawei |
| R3-212516 | [Draft] LS on QoE visibility at RAN | Huawei |
| R3-212641 | CB: # NRQoE5-RAN_visible - Summary of email discussion | Ericsson - moderator |
| 15.4 | Alignment of Radio-Related Measurement and QoE Measurements | |
| R3-211737 | Alignment of Radio-Related Measurement and QoE Measurements | Qualcomm Incorporated |
| R3-211841 | Discussion on Alignment of MDT and QoE Measurements | CATT |
| R3-211982 | Discussion on the alignment of Radio-Related Measurement and QoE Measurement | Samsung |
| R3-211991 | The Alignment of Radio-Related Measurements and QoE Measurements | Ericsson |
| R3-212326 | On the alignment of QoE measurements and MDT measurements | Nokia, Nokia Shanghai Bell |
| R3-212449 | Alignment of MDT and QoE Measurements | ZTE Corporation, China Telecom, China Unicom |
| R3-212452 | (TP for 38.401) Alignment of MDT and QoE Measurements | ZTE Corporation, China Telecom, China Unicom |
| R3-212453 | (TP for 38.473) Alignment of MDT and QoE Measurements | ZTE Corporation, China Telecom, China Unicom |
| R3-212455 | (TP for 38.463) Alignment of MDT and QoE Measurements | ZTE Corporation, China Telecom, China Unicom |
| R3-212496 | Alignment of radio related measurement and QoE measurement | CMCC |
| R3-212517 | Further analysis on spec impacts of the potential solutions to RAN assitsted measurement | Huawei |
| R3-212642 | CB: # NRQoE5-RRM_alignment - Summary of email discussion | Samsung - moderator |
| R3-212940 | CB: # NRQoE5-RRM_alignment - Summary of email discussion | Samsung - moderator |
| 16.1 | General | |
| R3-211443 | LS on support of PWS over SNPN | SA1 |
| R3-211454 | Reply LS on support of PWS over SNPN | SA2 |
| R3-211619 | Discussion of RAN3 impacts of supporting PWS over SNPN | Qualcomm Incorporated, Ericsson |
| R3-211620 | [DRAFT] Reply LS on LS on support of PWS over SNPN | Qualcomm Incorporated |
| R3-211709 | Work Plan for Enhancement for Private Network Support for NG-RAN WI | China Telecommunication |
| R3-212065 | Consideration on the enhanced NPN WI scopes | ZTE Corporation |
| R3-212156 | support of PWS over SNPN in R17 | Huawei |
| R3-212157 | [Draft] Reply LS on support of PWS over SNPN in R17 | Huawei |
| R3-212683 | CB: # 1001_PRN_Gen - Summary of email discussion | China Telecom - moderator |
| R3-212684 | CB: # 1002_PRN_PWS - Summary of email discussion | Huawei - moderator |
| R3-212801 | Reply LS on support of PWS over SNPN in R17 | Huawei |
| R3-212863 | Reply LS on support of PWS over SNPN in R17 | Huawei |
| 16.2.1 | Cell Access Control | |
| R3-211651 | Support for Access with Subscription owned by a Separate Entity | Nokia, Nokia Shanghai Bell |
| R3-211652 | Support for Onboarding and Remote Provisioning | Nokia, Nokia Shanghai Bell |
| R3-211653 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-211702 | RAN3 impacts of Enhancement of Private Network Support | Qualcomm Incorporated |
| R3-211703 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-211704 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-211804 | Discussion on cell access control for eNPN | CATT |
| R3-211899 | Supporting enhanced private network | Huawei |
| R3-211900 | Supporting enhanced private network | Huawei |
| R3-211901 | Supporting enhanced private network | Huawei |
| R3-212079 | (TP for TS 38.300) Introduce eNPN | ZTE Corporation |
| R3-212080 | Discussion on open issues of eNPN | ZTE Corporation |
| R3-212099 | Cell access control | Ericsson |
| R3-212192 | UE onboarding | Ericsson |
| R3-212446 | Support of access using credentials from credentials holder | LG Electronics Inc. |
| R3-212502 | Cell access and mobility aspects for NPN | CMCC |
| R3-212685 | CB: # 1003_PRN_Onboarding - Summary of email discussion | Nokia - moderator |
| R3-212818 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-212839 | Supporting enhanced private network | Huawei |
| R3-212850 | LS on Clarifications for eNPN key issues 1 and 4 | Nokia, Nokia Shanghai Bell |
| R3-212856 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-212864 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| R3-212865 | Introduction of support for eNPN | Qualcomm Incorporated |
| R3-212866 | Supporting enhanced private network | Huawei |
| R3-212867 | LS on clarifications on eNPN features | Nokia, Nokia Shanghai Bell |
| R3-212959 | Support for Enhanced Non Public Networks | Nokia, Nokia Shanghai Bell, China Telecom |
| 16.2.2 | Connected Mode Mobility Support | |
| R3-211710 | On mobility support for ePRN | China Telecommunication |
| R3-212081 | Consideration on mobility support for eNPN | ZTE Corporation |
| R3-212100 | Mobility | Ericsson |
| R3-212686 | CB: # 1004_PRN_Mobility - Summary of email discussion | Ericsson - moderator |
| 17.1 | General | |
| R3-212499 | TR 38.832 v0.5.0 | CMCC, ZTE |
| R3-212500 | Revised Work Plan for RAN Slicing | CMCC, ZTE |
| R3-212586 | Draft TR 38.832 v1.0.0 | CMCC, ZTE |
| R3-212648 | CB: # RANSlicing1-Workplan_Conclusion - Summary of email discussion | CMCC - moderator |
| R3-212943 | Draft TR 38.832 v1.1.0 | CMCC, ZTE |
| 17.3 | Solutions Evaluation and Conclusions | |
| R3-211452 | Reply LS on feedback on RAN WG3 service continuity solutions | SA2 |
| R3-211469 | Response to LS Reply LS on Enhancement of RAN Slicing | 3GPP SA5 |
| R3-211624 | (TP for TR38.832) Revised evaluation and conclusions | Qualcomm Incorporated |
| R3-211633 | Impact of SA5 feedback on Enhancement of RAN Slicing Slice Shortage solution | Nokia, Nokia Shanghai Bell |
| R3-211654 | Down-selection of Solutions for Slice not supported at target | Nokia, Nokia Shanghai Bell |
| R3-211842 | Discussion on Solutions Evaluation and Conclusions | CATT |
| R3-211902 | Final evaluation and conclusions of slicing service continuity | Huawei |
| R3-212070 | Conclusions on Enhancements for RAN Slicing | Ericsson |
| R3-212302 | Discussion on Slice Resource Remapping solutions | Ericsson |
| R3-212303 | Response to LS Reply on Enhancement of RAN Slicing | Ericsson |
| R3-212317 | Reply LS on feedback on RAN WG3 service continuity solutions | Ericsson |
| R3-212402 | Conclusion update on solutions for Scenarios 2 and 4 | LG Electronics Inc. |
| R3-212407 | Conclusion update on solutions for Scenarios 2, 4 | LG Electronics Inc. |
| R3-212420 | Discussion on down-selection for RAN slicing enhancement | Samsung, ZTE |
| R3-212501 | Solution down-selection and conclusion for service continuity | CMCC |
| R3-212574 | Further consideration on RAN slicing | ZTE, China Telecom ,Lenovo, Motorola Mobility,China Unicom |
| R3-212575 | (TP for BL CR for TR 38.832) RAN Slicing | ZTE, China Telecom,Lenovo, Motorola Mobility,China Unicom |
| R3-212649 | CB: # RANSlicing2-Slice_Conclusion - Summary of email discussion | ZTE - moderator |
| R3-212722 | Discussion on down-selection for RAN slicing enhancement | Samsung, ZTE, Verizon |
| R3-212773 | (TP for TR 38.832) RAN Slicing | ZTE |
| R3-212783 | (TP for TR 38.832) RAN Slicing | ZTE |
| R3-212804 | CB: # RANSlicing2-Slice_Conclusion - Summary of email discussion | ZTE - moderator |
| R3-212954 | (TP for TR 38.832) RAN Slicing | ZTE |
| R3-212977 | (TP for TR 38.832) RAN Slicing | ZTE |
| 17.4 | Others | |
| R3-211655 | Introduction of Slice Maximum Bit Rate | Nokia, Nokia Shanghai Bell |
| R3-211843 | Discussion on Supporting for UE-Slice-MBR | CATT |
| R3-211903 | Impact of SA2 slicing work on RAN | Huawei |
| R3-212576 | Support for UE-Slice-MBR | ZTE,China Telecom,China Unicom |
| R3-212646 | Response to R3-211655 | Ericsson Inc. |
| R3-212650 | CB: # RANSlicing3-Slice_SA2impact - Summary of email discussion | Nokia - moderator |
| R3-212914 | CB: # RANSlicing3-Slice_SA2impact - Summary of email discussion | Nokia - moderator |
| 18.1 | General | |
| R3-212506 | TR 37.817 v0.1.0 | CMCC |
| R3-212508 | Updated work plan for study on enhancement for data collection for NR and EN-DC | CMCC |
| R3-212687 | CB: # 44_DataColl_General - Summary of email discussion | CMCC - moderator |
| R3-212990 | TR 37.817 v0.2.0 | CMCC |
| 18.2 | High-Level Principles and Definitions | |
| R3-211615 | Functional Framework for RAN Intelligence to support different learning problems | Futurewei |
| R3-211632 | High-level principles and definitions for the AI/ML-based functional framework for RAN intelligence | Deutsche Telekom AG |
| R3-211681 | Discussion on open issues in section 4.2 Functional Framework | NEC |
| R3-211682 | TP to TR 37.817 section 4.2 Functional Framework | NEC |
| R3-211754 | AI/ML Architecture | Qualcomm Incorporated |
| R3-211968 | Discussion on Functional Framework | Samsung |
| R3-212027 | High-level framework and definition for AI RAN | ZTE Corporation |
| R3-212178 | Open issues of framework for AI | Lenovo, Motorola Mobility |
| R3-212189 | Discussion on framework of AI | CATT |
| R3-212299 | Functional Framework of AI/ML enabled NG-RAN Network | Intel Corporation |
| R3-212300 | High Level Principles and Definitions of AI/ML enabled NG-RAN | Intel Corporation |
| R3-212314 | Framework for RAN intelligence | Ericsson |
| R3-212372 | (TP for TR 37.817): AI/ML Framework Discussion | Nokia, Nokia Shanghai Bell |
| R3-212373 | (TP for TR 37.817): ML-related data support | Nokia, Nokia Shanghai Bell |
| R3-212503 | Further discussion on high-level framework for AI enabled RAN intelligence | CMCC |
| R3-212522 | Further discussion on the general frame work | Huawei |
| R3-212636 | Response to R3-211632, R3-211681, R3-211682, R3-211754, R3-211968, R3-212027, R3-212178, R3-212189, R3-212299, R3-212300, R3-212314, R3-212372, R3-212503, R3-212522 | NEC |
| R3-212688 | CB: # 45_DataColl_PrincDef - Summary of email discussion | Ericsson - moderator |
| R3-212841 | Framework for RAN intelligence | Ericsson |
| R3-212898 | Framework for RAN intelligence | Ericsson |
| R3-212978 | Framework for RAN intelligence | Ericsson |
| 18.3 | Use Cases for Artificial Intelligence in RAN and Potential Benefits | |
| R3-211669 | Machine Learning Use Case for BS Power Saving | Futurewei |
| R3-211683 | TP to TR 37.817 Use case description | NEC |
| R3-211969 | Discussion on Use Cases for RAN Intelligence | Samsung, Verizon Wireless |
| R3-212028 | AI based UE Trajectory Prediction | ZTE Corporation, China Unicom, Lenovo, Motorola Mobility, CMCC |
| R3-212029 | Solution to AI based UE Trajectory Prediction | ZTE Corporation, China Unicom, CMCC |
| R3-212030 | AI based Energy Saving | ZTE Corporation, China Unicom, Lenovo, Motorola Mobility |
| R3-212031 | Solution to AI based Energy Saving | ZTE Corporation, China Unicom |
| R3-212032 | AI based Load Prediction | ZTE Corporation, China Unicom, Lenovo, Motorola Mobility |
| R3-212033 | Solution to AI based load prediction | ZTE Corporation, China Unicom |
| R3-212179 | AI based PSCell change | Lenovo, Motorola Mobility |
| R3-212190 | Discussion on use cases for AI in RAN | CATT |
| R3-212191 | Discussion on UE Location prediction | CATT |
| R3-212269 | Data Forwarding Optimization Use Case for AI | InterDigital |
| R3-212271 | Mobility Optimization Use Case for AI | InterDigital |
| R3-212301 | Use cases for AI/ML enabled NG-RAN | Intel Corporation |
| R3-212313 | Overview of AI/ML use cases | Ericsson |
| R3-212315 | AI/ML for energy efficiency use case discussion | Ericsson |
| R3-212316 | AI/ML traffic steering use case discussion | Ericsson |
| R3-212389 | Use Cases and Requirements for Artificial Intelligence in RAN | AT&T |
| R3-212504 | AI-based load balancing | CMCC |
| R3-212507 | AI-based energy saving | CMCC |
| R3-212523 | Further discussions on detailed procedure and potential spec impacts of energy saving | Huawei |
| R3-212524 | Further discussion on AI/ML assisted load balancing | Huawei |
| R3-212689 | CB: # 46_DataColl_UseCases - Summary of email discussion | CMCC - moderator |
| R3-212807 | Further discussion on AI/ML assisted load balancing | Huawei |
| R3-212868 | TP for Mobility Optimization Use Case for TR 37.817 | InterDigital |
| R3-212890 | AI based Energy Saving | ZTE Corporation, China Unicom, Lenovo, Motorola Mobility |
| R3-212896 | AI based Energy Saving | ZTE Corporation, China Unicom, Lenovo, Motorola Mobility |
| 18.4 | Standards Impact on Existing Nodes, Functions, and Interfaces | |
| R3-211684 | TP to TR 37.817 Solutions and standard impacts | NEC |
| R3-211755 | Model training procedure | Qualcomm Incorporated |
| R3-211858 | Standards impact for identified use cases | CATT |
| R3-211970 | Discussion on Standard Impact for RAN Intelligence | Samsung |
| R3-212034 | Initial analyse on the interface impact with AI-based RAN architecture | ZTE Corporation, China Unicom |
| R3-212180 | Discussion on standard impact to support AI functionality | Lenovo, Motorola Mobility |
| R3-212371 | AI/ML Architecture Discussion | Nokia, Nokia Shanghai Bell |
| R3-212374 | General Principles of ML Functionality in RAN | Nokia, Nokia Shanghai Bell |
| R3-212465 | Discussion on Standard Impact for RAN Intelligence (Mobility Management) | Samsung |
| R3-212505 | Solutions for AI-based load balancing | CMCC |
| R3-212525 | Discussion on the correlation with other groups | Huawei |
| R3-212546 | Support of AI enabled Mobility for NG-RAN and EN-DC | LG Electronics |
| R3-212690 | CB: # 47_DataColl_StdImpact - Summary of email discussion | ZTE - moderator |
| R3-212895 | Initial analyse on the interface impact with AI-based RAN architecture | ZTE Corporation, China Unicom |
| R3-212897 | Initial analyse on the interface impact with AI-based RAN architecture | ZTE Corporation, China Unicom |
| 19.1 | General | |
| R3-212408 | Work Plan for NR Positioning Enhancements Work Item | Intel Corporation, CATT, Ericsson |
| 19.2.1 | Positioning Accuracy Improvements | |
| R3-211818 | Consideration on DL-AoD Positioning Solution | CATT |
| R3-211819 | Consideration on UL AOA Positioning Solution | CATT |
| R3-211820 | [Draft]Reply LS on DL-AoD angle calculation enhancement | CATT |
| R3-212221 | Discussion on positioning enhancement | Huawei |
| R3-212222 | Positioning enhancement | Huawei |
| R3-212237 | Discussion on positioning enhancement | Huawei |
| R3-212238 | Positioning enhancement | Huawei |
| R3-212239 | Positioning enhancement | Huawei |
| R3-212347 | Reply LS on DL-AoD angle calculation enhancement | Ericsson |
| R3-212348 | Discussion on first aspects related toRel-17 Positioning Accuracy Improvements | Ericsson |
| R3-212466 | Support of UL AoA Positioning enhancement | CATT |
| R3-212595 | LS on DL-AoD angle calculation enhancement | RAN1 |
| R3-212629 | CB: # 20_Pos_AoD - Summary of email discussion | CATT - moderator |
| R3-212691 | CB: # 51_Pos_AccEnhs_AoD_LS - Summary of email discussion | Ericsson - moderator |
| R3-212776 | CB: # 51_Pos_AccEnhs_AoD_LS - Summary of email discussion | Ericsson - moderator |
| R3-212780 | Introduction of NR Positioning enhancements to F1AP | Huawei |
| 19.2.2 | RRC_INACTIVE State Positioning | |
| R3-211821 | Discussion on RRC_INACTIVE State Positioning | CATT |
| R3-211983 | Positioning in RRC inactive state | Samsung |
| R3-212240 | Discussion on positioning for UE in RRC_INACTIVE state | Huawei |
| R3-212349 | Discussion on first aspects to support RRC-Inactive Positioning | Ericsson |
| R3-212350 | Support of NR Positioning in Inactive/Idle | Ericsson |
| R3-212692 | CB: # 52_Pos_RRC_INACTIVE - Summary of email discussion | Ericsson - moderator |
| 19.2.3 | On-Demand PRS Transmission and Reception | |
| R3-211779 | On-Demand DL-PRS | Qualcomm Incorporated |
| R3-211822 | Consideration on On-Demand PRS Transmission and Reception | CATT |
| R3-212225 | Discussion on on-demand PRS (with TP) | Huawei |
| R3-212241 | Discussion on on-demand PRS (with TP) | Huawei |
| R3-212351 | Discussion on first aspects to support On-Demand PRS transmission | Ericsson |
| R3-212352 | Support of NRPPa NR Positioning enhancements | Ericsson |
| R3-212353 | Support of F1AP NR Positioning enhancements | Ericsson |
| R3-212395 | On-demand PRS | Nokia, Nokia Shanghai Bell |
| R3-212693 | CB: # 53_Pos_OnDemandPRS - Summary of email discussion | Nokia - moderator |
| R3-212779 | Introduction of NR Positioning enhancements to NRPPa | Ericsson |
| 19.2.4.1 | GNSS Positioning Integrity Determination | |
| R3-212226 | Discussion on positioning integrity | Huawei |
| R3-212242 | Discussion on positioning integrity | Huawei |
| R3-212694 | CB: # 54_Pos_GNSSintegrity - Summary of email discussion | Huawei - moderator |
| 19.3 | Support for Latency Improvement | |
| R3-211780 | Scheduling Location in Advance to Reduce Latency | Qualcomm Incorporated |
| R3-211823 | Consideration on Latency Improvement | CATT |
| R3-211984 | Positioning latency improvement | Samsung |
| R3-212227 | Discussion on latency improvement | Huawei |
| R3-212243 | Discussion on latency improvement | Huawei |
| R3-212354 | Discussion on support of latency improvements for Rel-17 positioning | Ericsson |
| R3-212695 | CB: # 55_Pos_LatencyImprovement - Summary of email discussion | Huawei - moderator |
| 20.1 | General | |
| R3-211486 | Clarification of NAS Node Selection Function for NTN nodes providing access over multiple countries | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Huawei |
| R3-211487 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-211488 | Support of NTN RAT identification and NTN RAT restrictions | Qualcomm Incorporated, Huawei, Thales, , Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-211497 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated |
| R3-212228 | (TP for BL CR TS 38.300) NTN Stage 2 clean-up | Huawei |
| R3-212244 | (TP for BL CR TS 38.300) NTN Stage 2 clean-up | Huawei |
| R3-212696 | CB: # 77_NTN_General - Summary of email discussion | Thales - moderator |
| R3-212986 | Support Non-Terrestrial Networks | Huawei, Thales, Ericsson, ZTE, Qualcomm Incorporated |
| 20.2.1 | Network Identifier Handling | |
| R3-211707 | General usage of cell identity signalling in NGAP | Qualcomm Incorporated |
| R3-211815 | Discussion on CGI handling in RAN | CATT |
| R3-211896 | (TP for BL CR for TS 38.300) Cell ID handling on NG interface | Nokia, Nokia Shanghai Bell |
| R3-212109 | Discussion on handling and applicability of Network Identifiers on Xn and NG interface | Ericsson |
| R3-212229 | On mapping of the Cell identities of NTN cells | Huawai |
| R3-212245 | On mapping of the Cell identities of NTN cells | Huawei |
| R3-212476 | Discussion on Network Identifier Handling | CMCC |
| R3-212697 | CB: # 78_NTN_NW_IDhandling - Summary of email discussion | Qualcomm - moderator |
| R3-212789 | (TP for BL CR for TS 38.300) Cell ID handling on NG/Xn interface | Nokia, Nokia Shanghai Bell |
| 20.2.3 | Cell Relation Handling | |
| R3-211719 | Discussion on Cell relation handling | China Telecommunication |
| R3-212110 | Further discussion on neighbor relations and NTN | Ericsson |
| R3-212230 | Time Windows management for signalling reduction including TP for BL CRs | Huawei |
| R3-212246 | Time Windows management for signalling reduction including TP for BL CRs | Huawei |
| R3-212450 | Further Discussion on Cell Relation for NTN | ZTE |
| R3-212477 | Discussion on cell relation | CMCC |
| R3-212698 | CB: # 79_NTN_CellRelations - Summary of email discussion | Ericsson - moderator |
| 20.2.4 | Feeder Link Switch-Over for LEO | |
| R3-211720 | Further discussion on switch over for NTN | China Telecommunication |
| R3-211787 | NTN control data | THALES |
| R3-211816 | Further discussion on Feeder Link Switch | CATT |
| R3-211897 | Discussion on Feeder Link Switchover | Nokia, Nokia Shanghai Bell |
| R3-212419 | Discussion on enhancements for feeder link switch over | Samsung |
| R3-212454 | Further Discussion on LEO Feeder Link Switch-Over | ZTE |
| R3-212478 | Discussion on feeder link switch for NTN | CMCC |
| R3-212699 | CB: # 80_NTN_FeederSwitch - Summary of email discussion | Thales - moderator |
| R3-212794 | CB: # 80_NTN_FeederSwitch - Summary of email discussion | Thales - moderator |
| R3-212795 | TP for BL CR for 38.300 with normative and info annex | Thales, Huawei |
| R3-212936 | TP for BL CR for 38.300 with normative and info annex | Thales, Huawei |
| R3-212945 | TP for BL CR for 38.300 with normative and info annex | Thales, Huawei |
| 20.2.5 | Aspects Related to Country-Specific Routing | |
| R3-211418 | LS on UE location aspects in NTN | RAN2 |
| R3-211705 | Discussion of open issues related to LS traffic on CGI mapping, location information, and TAC update | Qualcomm Incorporated |
| R3-211706 | [DRAFT] Reply LS on UE location aspects in NTN | Qualcomm Incorporated |
| R3-211805 | Consideration on Location aspects in NTN | CATT |
| R3-211806 | [Draft] Reply LS on UE location aspects in NTN | CATT |
| R3-211817 | (TP for BL CR for TS 38.300)Clarification on country-specific CN selection | CATT |
| R3-211898 | (TP for BL CR for TS 38.413) Country Specific Routing for an RRC CONNECTED UE | Nokia, Nokia Shanghai Bell |
| R3-212114 | NTN and Location Reporting | Ericsson |
| R3-212115 | [DRAFT] [Reply] LS on location aspects in NTN | Ericsson |
| R3-212231 | Aspects Related to Country-Specific Routing, mobility for RRC Connected and RRC Inactive modes | Huawei |
| R3-212247 | Aspects Related to Country-Specific Routing, mobility for RRC Connected and RRC Inactive modes | Huawei |
| R3-212630 | CB: # 4_NTN_UElocation - Summary of email discussion | Qualcomm - moderator |
| R3-212700 | CB: # 81_NTN_CountrySpecificRouting - Summary of email discussion | Nokia - moderator |
| R3-212792 | [DRAFT] Reply LS on UE location aspects in NTN | Qualcomm Incorporated |
| R3-212793 | (TP for BL CR for TS 38.300)Clarification on country-specific CN selection | CATT |
| R3-212917 | Reply LS on UE location aspects in NTN | Qualcomm Incorporated |
| 20.2.6 | Others | |
| R3-211920 | NR-U plane protocol enhancement for NTN | Rakuten Mobile, Inc |
| R3-211921 | Non-Terrestrial Networks support for NR-U plane protocol | Rakuten Mobile, Inc |
| R3-212111 | Continuing Discussion on Xn Functions and NTN | Ericsson |
| R3-212701 | CB: # 82_NTN_Others - Summary of email discussion | Rakuten - moderator |
| 21.2 | Support for Propagation Delay Compensation Enhancements | |
| R3-211596 | Analysis of Propagation Delay Compensation enhancements | ZTE |
| R3-211597 | CR for TS38.413 on propagation delay compensation enhancements | ZTE |
| R3-211844 | Discussion on Propagation Delay Compensation Enhancements | CATT |
| R3-211904 | Network based propagation delay compensation | Huawei |
| R3-212050 | Discussion on Further enhanced NR-IIoT: Enhancements for support of time synchronization | Ericsson |
| R3-212051 | Enhancements for support of time synchronization | Ericsson |
| R3-212052 | Enhancements for support of time synchronization | Ericsson |
| R3-212379 | Time synchronization enhancements | Nokia, Nokia Shanghai Bell |
| R3-212397 | Discussion on the propagation delay compensation enhancements | Samsung |
| R3-212651 | CB: # NRIIOT1-PDC - Summary of email discussion | Nokia - moderator |
| 21.3 | Enhancements Based on New QoS Related Parameters | |
| R3-211598 | Analysis of New QoS Related parameters | ZTE |
| R3-211599 | CR for TS38.413 on new QoS related parameters | ZTE |
| R3-211613 | Further details of Survival Time | Nokia, Nokia Shanghai Bell |
| R3-211614 | Introduction of Survival Time to NGAP | Nokia, Nokia Shanghai Bell |
| R3-211845 | Discussion on new QoS related parameters | CATT |
| R3-211846 | CR to 38.413 on new QoS related parameters for IIOT | CATT |
| R3-211847 | CR to 38.423 on new QoS related parameters for IIOT | CATT |
| R3-211905 | Introduction of the survival Time | Huawei |
| R3-211906 | Introduction of the survival Time | Huawei |
| R3-211907 | Introduction of the survival Time | Huawei |
| R3-211962 | CR to 38.413 on new QoS related parameters for IIOT | CICT |
| R3-211966 | CR to 38.413 on new QoS related parameters for IIOT | CATT |
| R3-211967 | CR to 38.423 on new QoS related parameters for IIOT | CATT |
| R3-211992 | CR to 38.413 on new QoS related parameters for IIOT | CATT |
| R3-212078 | Introducing of further enhanced NR-IIoT | Ericsson |
| R3-212399 | Discussion on Discussion on supporting the survival time | Samsung |
| R3-212401 | CR for TS38.413 on including survival time in TSC Assistance Information enhancements | Samsung |
| R3-212403 | CR for TS38.423 on including survival time in TSC Assistance Information enhancements | Samsung |
| R3-212652 | CB: # NRIIOT2-New_QoS_Parameters - Summary of email discussion | Samsung - moderator |
| R3-212878 | CR to 38.413 on new QoS related parameters for IIOT | CATT |
| R3-212900 | Introduction of Enhanced IIoT support over NG | CATT, Nokia, Nokia Shanghai Bell, Samsung, Huawei, Ericsson, ZTE |
| R3-212901 | Introduction of Enhanced IIoT support over Xn | Ericsson, Samsung, Huawei, ZTE,CATT, Nokia, Nokia Shanghai Bell |
| R3-212902 | Introduction of Enhanced IIoT support over E1 | ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT, Huawei, Ericsson |
| R3-212903 | Introduction of Enhanced IIoT support over F1 | Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE, Samsung |
| 22.1 | General | |
| R3-211426 | Reply LS on 5MBS progress and issues to address | RAN2 |
| R3-211453 | Reply LS on 5MBS progress and issues to address | SA2 |
| R3-211471 | Introduction of MBS(BL CR for 38.463) | CATT |
| R3-211472 | Introduction of NR MBS | Lenovo, Motorola Mobility |
| R3-211478 | MBS BL CR for TS38.410 | ZTE |
| R3-211479 | Introduction of NR MBS | Huawei, CMCC |
| R3-211481 | Introduction of NR MBS | Samsung |
| R3-211482 | BL CR for NR MBS for 38.413 | Qualcomm Incorporated |
| R3-211484 | Introduction of NR MBS | LG Electronics |
| R3-211485 | Introduction of NR Multicast and Broadcast Services | Ericsson |
| R3-211496 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| R3-211515 | Reply LS on 5MBS progress and issues to address | RAN2 |
| R3-211541 | MBS BL CR for TS 38.410 | ZTE |
| R3-212092 | Discussion on the current status in SA2 and RAN2 | Ericsson |
| R3-212093 | [DRAFT] Reply LS on on 5MBS progress and issues to address | Ericsson |
| R3-212421 | Updated Rel-17 NR MBS work plan | Huawei, CMCC |
| R3-212422 | Discussion about LSs on 5MBS progress and issues to address | Huawei |
| R3-212423 | [DRAFT] Reply LS on 5MBS progress and issues to address | Huawei |
| R3-212479 | Introduction of MBS | CMCC |
| R3-212480 | Discussion on SA2 reply LS on 5MBS progress and issues to address | CMCC |
| R3-212481 | [Draft]Reply LS to SA2 on 5MBS Progress and Issues to address | CMCC |
| R3-212702 | CB: # 97_MBS_General - Summary of email discussion | Huawei - moderator |
| R3-212703 | CB: # 98_MBS_LSsProgress - Summary of email discussion | CMCC - moderator |
| R3-212790 | CB: # 98_MBS_LSsProgress - Summary of email discussion | CMCC - moderator |
| R3-212982 | Introduction of NR MBS | Nokia, Nokia Shanghai Bell |
| 22.2.2 | Session Management over NG | |
| R3-211542 | MBS session management and TP to 38.410 38.413 BL CR | ZTE |
| R3-211543 | TP to 38.414 MBS BL CR on IP multicast | ZTE |
| R3-211656 | (TP for 38.300 & 38.410) Stage 2 for Multicast and Broadcast | Nokia, Nokia Shanghai Bell |
| R3-211657 | (TP for 38.413) Setup of MBS Context and UE MBS Context | Nokia, Nokia Shanghai Bell |
| R3-211658 | (TP for 38.413) Management of User Plane Shared Delivery Tunnel | Nokia, Nokia Shanghai Bell |
| R3-211751 | NR Multicast Session Management Procedure | Qualcomm Incorporated |
| R3-211876 | TP for 38.413 on session management for broadcast service | CATT,CBN, Huawei |
| R3-211877 | Discussion on MBS session management for multicast | CATT |
| R3-211971 | TP for MBS BLCR for 38.413-Session management for MBS over NG | Samsung |
| R3-212101 | [TP for BL CR for 38.300 and TS 38.410] Session Management over NG and its application on Xn | Ericsson |
| R3-212102 | [TP for BL CR for 38.413 and TS 38.423] on MBS Session Management | Ericsson |
| R3-212181 | Multicast Session Management over NG | Lenovo, Motorola Mobility |
| R3-212385 | Discussion on a group notification towards NG-RAN supporting MBS | LG Electronics |
| R3-212424 | (TP to TS 38.410 BL CRs) Multicast Session Management | Huawei, CBN |
| R3-212425 | (TP to TS 38.413 BL CRs) Multicast Session Management | Huawei, CBN |
| R3-212482 | MBS Session management over NG | CMCC |
| R3-212483 | (TP to TS 38.410 ) MBS session management over NG | CMCC |
| R3-212484 | (TP to TS 38.300 ) MBS session management over NG | CMCC, Huawei |
| R3-212704 | CB: # 100_MBS_NGsessMgmt - Summary of email discussion | Ericsson - moderator |
| 22.2.3 | Dynamic Change Between PTP and PTM for UEs in RRC_CONNECTED State | |
| R3-211544 | Mode switching for NR MBS | ZTE |
| R3-211659 | (TP for 38.300 & 38.401 & 38.470) Stage 2 for PTP-PTM Switching | Nokia, Nokia Shanghai Bell |
| R3-211866 | Discussion on dynamic change between PTM and PTP | CATT |
| R3-211975 | TP for TS38.463 BL: Dynamic Change Between PTP and PTM | Samsung |
| R3-212103 | On PTP and PTM Switch | Ericsson |
| R3-212182 | (TP for BL CR 38.401) Dynamic switch between PTP and PTM | Lenovo, Motorola Mobility |
| R3-212386 | Issues on dynamic change between PTP and PTM | LG Electronics |
| R3-212426 | (TP to TS 38.401 BL CR) Decision on PTP and PTM | Huawei, CBN |
| R3-212485 | Discussion on dynamic change between PTP and PTM | CMCC |
| R3-212705 | CB: # 101_MBS_PTP-PTMdynChg - Summary of email discussion | Huawei - moderator |
| R3-212713 | CB: # 50_eNBarchEvo_AP - Summary of email discussion | Huawei - moderator |
| 22.2.4 | Bearer Management over F1/E1 | |
| R3-211545 | MBS bearer management over F1 and E1 and TPs to 38.470 38.473 38.460 38.463 BL CR | ZTE |
| R3-211660 | (TP for 38.401) MBS F1, E1 Bearer Management | Nokia, Nokia Shanghai Bell |
| R3-211873 | Further Consideration on MBS context management over F1 and E1 | CATT |
| R3-211874 | TP for 38.463 on MBS Bearer Management for broadcast at E1 interface | CATT |
| R3-211875 | TP for 38.473 on MBS Context Management for Broadcast at F1 interface | CATT |
| R3-211974 | TP for TS38.473 BL: Introduction of NR MBS | Samsung |
| R3-212104 | [TP for BL CR for 38.473 and TS 38.463] On F1 and E1 protocol aspects for NR MBS | Ericsson |
| R3-212183 | Bearer Management over F1/E1 for Multicast Session | Lenovo, Motorola Mobility |
| R3-212184 | User Plane Protocol Aspects of F1-U for NR MBS | Lenovo, Motorola Mobility |
| R3-212436 | (TP to TS 38.401 BL CR) Bearer management over F1 and E1 | Huawei, CBN |
| R3-212437 | (TP to TS 38.470 and 38.460 BL CRs) Bearer management over F1 and E1 interfaces | Huawei, CBN |
| R3-212486 | Discussion on MBS Bearer Management | CMCC |
| R3-212706 | CB: # 102_MBS_F1-E1bearerMgmt - Summary of email discussion | CATT - moderator |
| R3-212791 | CB: # 102_MBS_F1-E1bearerMgmt - Summary of email discussion | CATT - moderator |
| 22.2.5 | Others | |
| R3-211546 | MBS service area | ZTE |
| R3-212185 | MBS Service Area Management | Lenovo, Motorola Mobility |
| R3-212707 | CB: # 43_MBS_ServiceArea - Summary of email discussion | Lenovo - Moderator |
| 22.3.1 | Mobility Between MBS Supporting Nodes | |
| R3-211547 | Discussion on lossless Mobility in NR MBS | ZTE |
| R3-211548 | Discussion on MBS mobility procedure | ZTE |
| R3-211661 | (TP for 38.415) Seamless Mobility between two MBS Supporting Nodes | Nokia, Nokia Shanghai Bell |
| R3-211662 | (TP for 38.300) MBS Stage 2 for Mobility Management | Nokia, Nokia Shanghai Bell |
| R3-211663 | Realization of Data Forwarding to minimize packet loss | Nokia, Nokia Shanghai Bell |
| R3-211752 | Data forwarding in multicast handover | Qualcomm Incorporated |
| R3-211867 | Discussion on multicast context establishment during Xn-based handover | CATT |
| R3-211868 | Possible solutions on PDCP sync while keeping MRB mapping flexible | CATT |
| R3-211869 | Draft LS on aligning MRB PDCP Count among multiple gNBs | CATT |
| R3-211870 | TP on TS 38.300 on aligning MRB PDCP Count among multiple gNBs | CATT |
| R3-211972 | Coordinated assignment of PDCP SN | Samsung |
| R3-211973 | Data forwarding for mobility between MBS supporting nodes | Samsung |
| R3-212105 | On Support of mobility between gNBs supporting MBS | Ericsson |
| R3-212106 | [TP for BL CR TS 38.300] HO between supporting gNBs | Ericsson |
| R3-212107 | [TP for BL CR TS 38.401 and TS 38.463] HO between supporting gNBs | Ericsson |
| R3-212186 | Enhancements to support loss-less handover for NR multicast | Lenovo, Motorola Mobility |
| R3-212388 | Handling on Mobility between MBS Supporting Nodes | LG Electronics |
| R3-212427 | (TP to TS 38.300 BL CR) Mobility between MBS supporting nodes | Huawei, CBN, CMCC |
| R3-212428 | (TP to TS 38.401 BL CR) Mobility between MBS Supporting Nodes | Huawei, CBN |
| R3-212429 | (TP to TS38.300 BL CR) Consideration on DL PDCP Synchronization | Huawei, CBN, China Unicom, CMCC |
| R3-212430 | (TP to TS38.300 BL CR) Data forwarding between MBS supporting nodes | Huawei, CBN, China Unicom, China Telecom |
| R3-212438 | (TP to TS 38.415 BL CR) Support of NR MBS data transmission | Huawei, CBN, China Telecom, China Unicom |
| R3-212487 | Discussion on Mobility with Service Continuity | CMCC |
| R3-212708 | CB: # 103_MBS_MobilitySupporting - Summary of email discussion | Qualcomm - moderator |
| 22.3.2 | Mobility Between MBS Supporting and non-MBS Supporting Nodes | |
| R3-211549 | Discussion on UE mobility between an MBS-supporting gNB and a non-MBS-supporting gNB | ZTE |
| R3-211664 | (TP for 38.300) Mobility with non-MBS supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
| R3-212108 | On support of mobility between MBS supporting and non-MBS supporting gNBs | Ericsson |
| R3-212187 | Mobility between MBS Supporting and non-Supporting nodes | Lenovo, Motorola Mobility |
| R3-212431 | (TP to TS38.300 BL CR) Mobility between MBS supporting and non-supporting nodes | Huawei, CBN, China Telecom, China Unicom |
| R3-212488 | Discussion on Mobility from non-MBS-supporting node to MBS-supporting node | CMCC |
| R3-212489 | Discussion on Mobility from MBS-supporting node to non-MBS-supporting node | CMCC |
| R3-212709 | CB: # 104_MBS_MobilityNonSupporting - Summary of email discussion | Nokia - moderator |
| R3-212788 | (TP for 38.300) Mobility with non-MBS supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
| R3-212908 | (TP for 38.300) Mobility with non-MBS supporting NG-RAN nodes | Nokia, Nokia Shanghai Bell |
| 22.4 | Others | |
| R3-211550 | Discussion on Broadcast service continuity in NR MBS | ZTE |
| R3-211753 | MBS Session Context Transfer for mobility and SFN | Qualcomm Incorporated |
| R3-211872 | MBS reception of Idle and In-active UEs | CATT |
| R3-212439 | (TP to TS 38.300 BL CR) Service reception continuity for broadcast service | Huawei, CBN |
| R3-212593 | Effect of NR MBS related network planning on NG-RAN architecture | Chengdu TD Tech, TD Tech |
| R3-212710 | CB: # 99_MBS_Others - Summary of email discussion | Huawei - moderator |
| 23.2.1 | General Principles, Functions and Procedures | |
| R3-212022 | Further discussions on implementing PDCP for legacy case and NG-RAN case | Huawei, China Unicom |
| R3-212023 | CR to 38.401 on the introduction of ng-eNB CP-UP separation | Huawei, CMCC, China Unicom |
| R3-212024 | CR to 36.401 on the introduction of eNB CP-UP separation | Huawei, China Unicom |
| R3-212193 | CP-UP separation for eNBs | Ericsson |
| R3-212196 | General principles for eNB CP-UP separation | Ericsson |
| R3-212526 | Further discussions on logical entities and corresponding definitions | Huawei, CMCC, CUC |
| R3-212711 | CB: # 48_eNBarchEvo_General - Summary of email discussion | Huawei - moderator |
| R3-212825 | Further discussions on logical entities and corresponding definitions | Huawei, Ericsson |
| R3-212885 | Further discussions on logical entities and corresponding definitions | Huawei, Ericsson |
| R3-212938 | Further discussions on logical entities and corresponding definitions | Huawei, Ericsson |
| 23.2.2 | Signaling Transport | |
| R3-212025 | Further discussions on signalling transport for the new interface | Huawei |
| R3-212026 | CR to 38.462 on the introduction of new interface | Huawei |
| R3-212194 | E1 Signaling Transport for eNB CP-UP separation | Ericsson |
| R3-212197 | E1 Signaling Transport for eNB CP-UP separation | Ericsson |
| R3-212712 | CB: # 49_eNBarchEvo_SigTran - Summary of email discussion | Ericsson - moderator |
| R3-212827 | CR to 38.462 on the introduction of new interface | Huawei, Ericsson |
| R3-212835 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei |
| R3-212836 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei |
| R3-212859 | CR to 36.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-212860 | CR to 38.401: Baseline CR for introducing Rel-17 Enhanced eNB Architecture Evolution | Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| 23.2.3 | Application Protocol | |
| R3-212195 | E1 changes needed for eNB CP-UP separation | Ericsson |
| R3-212198 | E1 changes needed for eNB CP-UP separation | Ericsson |
| R3-212527 | Further discussion on stage 3 details | Huawei |
| R3-212528 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB | Huawei |
| R3-212826 | CR to 38.463 on the support of CP-UP separation for eNB and ng-eNB | Huawei, Ericsson |
| 30 | Other WIs/SIs Impacting RAN3 | |
| R3-211510 | LS on NAS-based busy indication | RAN2 |
| R3-211514 | Reply LS on small data transmission | TSG RAN WG2 |
| R3-211570 | Discussion on SDT with/without UE context relocation | ZTE |
| R3-211571 | Draft LS for further Reply LS on small data transmission | ZTE |
| R3-211572 | CR 38.300 for support of small data transmission | ZTE |
| R3-211573 | Discussion on NAS-based busy indication | ZTE |
| R3-211574 | Draft reply LS for NAS-based busy indication | ZTE |
| R3-211688 | Enhancement of Retrieve UE Context procedure to support SDT | NEC |
| R3-211689 | (TP for SDT BL CR for TS 38.423) SDT support with and without UE context relocation | NEC |
| R3-211708 | Discussion on RAN3 impacts of NR small data transmission | Qualcomm Incorporated |
| R3-211743 | NAS based busy indication | Qualcomm Incorporated |
| R3-211783 | Common aspects for NR SDT | Ericsson |
| R3-211790 | Support for Multi-USIM devices | Nokia, Nokia Shanghai Bell |
| R3-211791 | Support for Multi-USIM devices | Nokia, Nokia Shanghai Bell |
| R3-211792 | Support for Multi-USIM devices | Nokia, Nokia Shanghai Bell |
| R3-211809 | Discussion on SDT data transmission | CATT |
| R3-212019 | Discussion on NAS-based busy indication | Huawei |
| R3-212020 | [DRAFT] Reply LS on NAS-based busy indication | Huawei |
| R3-212346 | WI work plan for RedCap | Ericsson |
| R3-212396 | RLC PDU Handling in Small Data Transmission | China Telecomunication Corp. |
| R3-212432 | Support of RACH based small data transmission | Huawei |
| R3-212577 | Consideration on small data transmission without anchor relocation | LG Electronics Inc. |
| R3-212631 | CB: # 34_SDT_[LOW-PRIO] - Summary of email discussion | Ericsson - moderator |
| R3-212632 | CB: # 35_MultiUSIM_[LOW-PRIO] - Summary of email discussion | ZTE - moderator |
| R3-212714 | Response to R3-211574 | Nokia, Nokia Shanghai Bell |
| R3-212820 | Reply LS on small data transmission | Ericsson |
| R3-212877 | Reply LS on NAS-based busy indication | ZTE |
| 31.2.1 | Local NG-RAN Node Identifier | |
| R3-211586 | Discussion on I-RNTI partitioning | ZTE |
| R3-211587 | CR38423 for addition of I-RNTI structure indication | ZTE |
| R3-211665 | Support of Local NG-RAN node identifier | Nokia, Nokia Shanghai Bell |
| R3-211666 | Resolution of NG-RAN Node ID from I-RNTI | Nokia, Nokia Shanghai Bell |
| R3-212014 | NG-RAN node ID resolution from I-RNTI | Huawei |
| R3-212015 | NG-RAN node ID resolution from I-RNTI [INACTIVE_Local_Node_Id] | Huawei |
| R3-212310 | Node Identifier for RRC Inactive | Ericsson, Bell Mobility |
| R3-212311 | Addition of multiple Local NG-RAN Identifiers per NG-RAN node | Ericsson, Bell Mobility |
| R3-212633 | CB: # 33_LocalNG-RANnodeID - Summary of email discussion | Ericsson - moderator |
| 31.2.2 | RRC Reject Template for the gNB-DU | |
| R3-211692 | Discussion on RRC Reject Template | Nokia, Nokia Shanghai Bell |
| R3-211693 | RRC Reject Template [REJECT_TEM] | Nokia, Nokia Shanghai Bell |
| 32 | Any other business | |
| R3-212951 | Final Remarks | RAN3 Chairman |